Skip to content
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

Update CRT submodules to latest releases #1069

Merged
merged 3 commits into from
Oct 17, 2024
Merged

Conversation

unexge
Copy link
Contributor

@unexge unexge commented Oct 17, 2024

Description of change

Notably, includes awslabs/aws-c-s3#457.

Size:

$ cargo package -p mountpoint-s3-crt-sys --no-verify --allow-dirty
   Packaging mountpoint-s3-crt-sys v0.9.0 (~/Code/mountpoint-s3/mountpoint-s3-crt-sys)
    Packaged 2132 files, 38.3MiB (6.8MiB compressed)
CRT changelog:
Submodule mountpoint-s3-crt-sys/crt/aws-c-common f8c5d8e5..f58e807d:
  > Fix Cmake Prebuild Remove -S Option (#1158)
  > improve condition_variable documentation (#1157)
Submodule mountpoint-s3-crt-sys/crt/aws-c-io dc41ddc4..e3637404:
  > Add network interface name validation api (#675)
  > Handle PKCS#8 private keys in Windows (#683)
Submodule mountpoint-s3-crt-sys/crt/aws-c-s3 ab70f742..16701501:
  > Retry RequestTimeout error by S3.  (#457)
  > Validate Invalid Network Interface Names at Client Initialization  (#456)

Does this change impact existing behavior?

No breaking changes, aws-c-s3 now retries on RequestTimeout from S3.

Does this change need a changelog entry in any of the crates?

Yes, updated.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

Signed-off-by: Burak Varlı <burakvar@amazon.co.uk>
IsaevIlya
IsaevIlya previously approved these changes Oct 17, 2024
CRT was returning error during first operation before if it provided
with a non-existent network interface name. But with
awslabs/aws-c-s3#456, it started failing
during the client creation phase. Our tests were written for the
previous behaviour and was expecting client creation to succeed even
with an invalid network interface. The test is updated to expect
errors during client creation.

Signed-off-by: Burak Varlı <burakvar@amazon.co.uk>
IsaevIlya
IsaevIlya previously approved these changes Oct 17, 2024
Copy link
Contributor

@monthonk monthonk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one comment on changelog and should be ready to merge.

mountpoint-s3-client/CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Monthon Klongklaew <monthonk@amazon.com>
Signed-off-by: Burak <unexge@gmail.com>
Copy link
Contributor

@monthonk monthonk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@monthonk monthonk added this pull request to the merge queue Oct 17, 2024
Merged via the queue into awslabs:main with commit 587df3b Oct 17, 2024
23 checks passed
@unexge unexge deleted the update-crt branch October 17, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants