mark_process_dead: avoid error with bad env #768
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When the multiprocess environemnt is not properly set-up (missing environment variable) and mark_process_dead is called, the method raises an error on path.join() because the path is None which may be problematic This commit simply ignores the cleanup when the variable is not present Signed-off-by: Romuald Brunet <romuald@gandi.net>
romuald
force-pushed
the
mark_process_dead-without-env
branch
from
1fbdd40 to
d8d4248
Compare
csmarchbanks
reviewed
Feb 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the multiprocess environemnt is not properly set-up (missing
environment variable) and mark_process_dead is called, the method raises
an error on path.join() because the path is None which may be
problematic
This commit simply ignores the cleanup when the variable is not present
Context
We are using the same library for multiprocess and non-multiprocess setups.
While the setup is obviously wrong on our part (adding
mark_process_deadusingatexit). I thought that check in prometheus_client would be nice addition if anyone would get in the same pitfall