I hereby claim:
- I am datagrok on github.
- I am datagrok (https://keybase.io/datagrok) on keybase.
- I have a public key ASCrSLf3jYbRq3V0I7pJgP1UEqtjxqqP5iTBLfN5VXNq-Qo
To claim this, I am signing this object:
Michael F. Lamb datagrok
This article is now published on my website: When are circular imports fatal?
Unfinished draft; do not use until this notice is removed.
We were seeing some unexpected behavior in the processes that Jenkins launches when the Jenkins user clicks "cancel" on their job. Unexpected behaviors like:
- apparently stale lockfiles and pidfiles
- overlapping processes
- jobs apparently ending without performing cleanup tasks
- jobs continuing to run after being reported "aborted"
This article is now published on my website: Shared directory gotchas.
The scripts previously contained in this gist have moved to datagrok/modular-git-hooks/hooks.
datagrok
/ if_i_ran_the_company.md
Last active
January 14, 2019 07:36
If I ran a company, what would it look like?
The article previously hosted at this location is now published on my website: If I Ran The Company.
datagrok
/ AGPL3-modifications.md
Last active
January 14, 2019 07:43
Some questions and answers about various Free Software licenses.
This article previously hosted here is now published on my website: AGPLv3 affects only derivatives?
Python has a built-in variable __debug__ which is set to True when python is called without -O (optimize). The -O flag disables all assertion code.
This seems at first glance like a very easy and clean construct to rely on when coding in development versus production: in development, don't use -O, defensively litter your code with type- and sanity-checking asserts. Perform development-only debugging by testing __debug__ beforehand.
When in production, run all code is run with -O which disables asserts (speeding execution) and sets __debug__ to False.
From a comment on StackOverflow:
Vendoring is the moving of all 3rd party items such as plugins, gems and even rails into the /vendor directory. This is one method for ensuring that all files are deployed to the production server the same as the dev environment.
The activity described above, on its own, is fine. It merely describes the deployment location for various resources in an application.
The article previously hosted here is now published on my website: My ErgoDox Keyboard.
NewerOlder