-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bind out cross-process lock with unit tests. #519
Merged
Merged
Changes from 11 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
2d63fc3
Added cross process locking api for S3.
JonathanHenson 79b9375
Added cross process locking api for S3.
JonathanHenson 30341b3
refactor test slightly.
JonathanHenson 3b87cf9
use my fix short-term.
JonathanHenson 08ce439
fix clang-format's complaints.
JonathanHenson 9ca4769
try again on musl
JonathanHenson a935134
Update awscrt/s3.py
JonathanHenson ad1c950
address PR feedback.
JonathanHenson 67f530a
fix python formatter.
JonathanHenson 743ad37
another attempt on formatter.
JonathanHenson 83b36b9
ran formatter.
JonathanHenson ccd73a2
update to actual release tag.
JonathanHenson File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Submodule aws-c-common
updated
14 files
+19 −3 | .github/workflows/ci.yml | |
+23 −0 | include/aws/common/allocator.h | |
+35 −0 | include/aws/common/cross_process_lock.h | |
+24 −0 | include/aws/common/priority_queue.h | |
+64 −13 | source/allocator.c | |
+105 −0 | source/posix/cross_process_lock.c | |
+24 −0 | source/priority_queue.c | |
+2 −2 | source/task_scheduler.c | |
+93 −0 | source/windows/cross_process_lock.c | |
+10 −0 | tests/CMakeLists.txt | |
+39 −4 | tests/alloc_test.c | |
+116 −0 | tests/cross_process_lock_tests.c | |
+36 −0 | tests/priority_queue_test.c | |
+16 −1 | tests/system_resource_util_test.c |
This file contains 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 file contains 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 file contains 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 file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the CRT have any formalized error hierarchy in Python? I haven't dug too deeply yet. My only concern here is RuntimeError is very generic so it will be difficult to do control flow handling with this without message introspection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@graebm any thoughts here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not great. It's the same problem we have in every language binding. We didn't code-gen error classes, so catching specific CRT errors means users must catch a RuntimeError and introspect it.
In this specific case, we could dance around the issue and just return None or False if the C function returns NULL, since we do often expect it to fail 🤷♀️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not happy about this. I really want to do a mildly-breaking-change to all our bindings and address this issue. But it's non-trivial :|