[HOTFIX] Fixing crash on startup of tuplex.Context() due to missing AWS credentials #5
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
This was
linked to
issues
Jul 6, 2021
|
Thanks for the quick response! I can confirm this happens on the straight pip install on Linux too, assuming the fix will apply to that platform as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 no AWS credentials are specified (i.e. via
aws configureor using environment variablesAWS_SECRET_ACCESS_KEY/AWS_ACCESS_KEY_ID) a segfault is produced due to a buggy Boost.Python exception translation.Version should be pushed to 0.3.0.post1 or better even 0.3.1 to avoid frustration of pulling a segfaulting package.