Fix crash caused by faulty call to logger #829
Merged
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.
I was setting up a local database for testing Explorer, and
cubedash-gen
was throwing stack traces left right and center at me.It only occurred with multiple jobs, which is the default.
I suspected it's something we're doing wrong with
structlog
, on the structlog Performance page it says to not usecache_logger_on_first_use=True
if you're passing loggers around withmultiprocessing
, which is whatcubedash-gen
uses for running in parallel.But, that didn't fix it.
What did fix it was changing the line that was the top of the exception to take a kwarg instead of an arg. I don't know why this works, but, it does, and I've spent too long debugging!
📚 Documentation preview 📚: https://datacube-explorer--829.org.readthedocs.build/en/829/