Update uAMQP vendor #393
Merged
Update uAMQP vendor #393
Conversation
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
kashifkhan
force-pushed
the
uamqp_vendor_update
branch
from
7c86107
to
71b6613
Compare
swathipil
force-pushed
the
uamqp_vendor_update
branch
from
cfe2116
to
92fc5fa
Compare
benbp
reviewed
Aug 21, 2024
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.
Pulling upstream changes to vendored uamqp-c.
Live test run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4077788&view=results
Need to investigate the following SB SDK test failures:
test_queue_complete_message_on_different_receiver, which was added to the most recent PR of SB but has not been releasedHowever, these are not failing locally with the wheels installed, so merging the fix.