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

re-enable content length enforcement #3618

Merged
merged 1 commit into from
May 13, 2024

Conversation

aajtodd
Copy link
Contributor

@aajtodd aajtodd commented Apr 30, 2024

Motivation and Context

This PR re-enables content-length runtime plugin that was previously disabled due to some erroneous tests. Those tests appear to be fixed.

Original PR: #3491
Tracking issue: #3523

Checklist

  • I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link

A new generated diff is ready to view.

  • AWS SDK (ignoring whitespace)
  • No codegen difference in the Client Test
  • No codegen difference in the Server Test
  • No codegen difference in the Server Test Python
  • No codegen difference in the Server Test Typescript

A new doc preview is ready to view.

@aajtodd
Copy link
Contributor Author

aajtodd commented May 1, 2024

Blocked by #3620 landing and a new version of the SDK released with that test ignored so that semver hazards check can pass.

github-merge-queue bot pushed a commit that referenced this pull request May 1, 2024
## Motivation and Context

#3618 is blocked by semver
hazards check because the current version of this test in `aws-sdk-rust`
expects the test to
[panic](https://github.com/smithy-lang/smithy-rs/blob/release-2024-04-30/aws/sdk/integration-tests/s3/tests/streaming-response.rs#L23).
To land the content length enforcement PR we need to ignore the test and
release `smithy-rs` and a version of the SDK with the test ignored
instead of expecting it to panic.

----

_By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice._
ogghead pushed a commit to ogghead/smithy-rs that referenced this pull request May 5, 2024
## Motivation and Context

smithy-lang#3618 is blocked by semver
hazards check because the current version of this test in `aws-sdk-rust`
expects the test to
[panic](https://github.com/smithy-lang/smithy-rs/blob/release-2024-04-30/aws/sdk/integration-tests/s3/tests/streaming-response.rs#L23).
To land the content length enforcement PR we need to ignore the test and
release `smithy-rs` and a version of the SDK with the test ignored
instead of expecting it to panic.

----

_By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice._
@aajtodd aajtodd force-pushed the atodd/enable-content-length-enforcement branch from cd46750 to 16cdfe1 Compare May 13, 2024 18:47
@aajtodd aajtodd removed the blocked label May 13, 2024
@aajtodd aajtodd marked this pull request as ready for review May 13, 2024 18:51
@aajtodd aajtodd requested review from a team as code owners May 13, 2024 18:51
Copy link

A new generated diff is ready to view.

  • AWS SDK (ignoring whitespace)
  • No codegen difference in the Client Test
  • No codegen difference in the Server Test
  • No codegen difference in the Server Test Python
  • No codegen difference in the Server Test Typescript

A new doc preview is ready to view.

@aajtodd aajtodd added this pull request to the merge queue May 13, 2024
Merged via the queue into main with commit 1117dc7 May 13, 2024
44 checks passed
@aajtodd aajtodd deleted the atodd/enable-content-length-enforcement branch May 13, 2024 20:35
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.

None yet

3 participants