VirtualTam's bookmarks
12 bookmarks found
Page 1 of 1
-
Open questions, potential solutions or workarounds:
- Loki does not support out-of-order message ingestion
- There is not Java client for Loki
- The Wiced MQTT queue might be limited depending on the volume of logs
-
Kubernetes Best Practices - GCP Blog
2018-09-28 - https://cloudplatform.googleblog.com/2018/04/Kubernetes-best-practices-how-and-why-to-build-small-container-images.html
- https://cloudplatform.googleblog.com/2018/04/Kubernetes-best-practices-Organizing-with-Namespaces.html
- https://cloudplatform.googleblog.com/2018/05/Kubernetes-best-practices-Setting-up-health-checks-with-readiness-and-liveness-probes.html
- https://cloudplatform.googleblog.com/2018/05/Kubernetes-best-practices-Resource-requests-and-limits.html
- https://cloudplatform.googleblog.com/2018/05/Kubernetes-best-practices-terminating-with-grace.html
- https://cloudplatform.googleblog.com/2018/05/Kubernetes-best-practices-mapping-external-services.html
- https://cloudplatform.googleblog.com/2018/06/Kubernetes-best-practices-upgrading-your-clusters-with-zero-downtime.html
-
Nigel Tufnel Day
2016-03-23 In the run-up to 2011 Spinal Tap fans created a movement to make 11/11/11 "Nigel Tufnel Day." The movement was organised by The Nigel Tufnel Day Appreciation Society and Quilting Bee in Favor of Declaring & Observing November 11, 2011 as Nigel Tufnel Day (in Recognition of Its Maximum Elevenness). The theme of Nigel Tufnel Day was to take whatever you are doing on that day and "turn it up to 11".
-
D'Addario String Tension Pro
2015-08-31 Tension / gauge calculator to design custom string sets
Related threads:
- http://www.talkingbass.net/flappy-b-strings-tight-d-strings-and-the-switch-to-progressive-tension/
- http://www.mcdonaldstrings.com/stringxxiii.html (limited support for open/drop tunings, no 7+ string support, no bass support)
-
Python unit testing frameworks: Nose, Pytest
2015-02-13 Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)
I'm currently looking for more dev-friendly solutions, the key points being:
- writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
- parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
- complete feature set!
- we don't want to just run tests...
- coverage reports (find dead/weak/untested code sections)
- output formatting (JUnit-XML seems to be quite a common format out there)
There seem to be 3 solutions in Python:
- stock unittest + project-dependent customizations / test helpers
- nosetests
- py.test
And 2 ways of gettings things done:
- keeping things stock: no external dependency, project-specific implementation...
- using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)
Some links:
Page 1 of 1