[pull] main from awslabs:main #5
Merged
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
To support these new protocols, we also changed the runtime Router definition as for both awsJson 1.0 and 1.1, every request MUST be sent to the root URL (/) using the HTTP "POST" method. The runtime Router now supports explicitly all the available protocols. There are still some protocol tests failing for awsJson 1.0 and 1.1. The failure are caused by the missing implementation of @endpoint trait and date parsing. Protocol tests for these 2 protocols are heavily biased towards Responses. Before announcing support for awsJson 1.0 and 1.1, we should increase the protocol tests coverage. Signed-off-by: Bigo <[email protected]> Co-authored-by: david-perez <[email protected]>
* Upgrade to Smithy 1.16.2 * Remove extra test fixed in Smithy 1.16.2 * Upgrade to Smithy 1.16.3 * Remove extra test fixed in Smithy 1.16.3 * Remove failing expectation from server tests * Upgrade to Smithy 1.17.0 * Upgrade to Smithy 1.18.1 * Upgrade to Smithy 1.19.0 * Upgrade to Smithy 1.21.0 * Update changelog * Fix Gradle repositories
In #1268, runtime crates were updated to Rust 2021 edition. Co-authored-by: Russell Cohen <[email protected]>
…eam from a file (#1238) * Allow to specify a read buffer initial capacity when creating ByteStream from a file The behaviour of the existing ByteStream::from_file / ByteStream::from_path is unchanged (using a default buffer capacity of 4k, which corresponds to Tokio's ReaderStream default buffer capacity). Using higher buffer sizes can result in a large reduction in CPU during S3 uploads, at the cost of memory increase. * Rename len to file_size This makes the distinction with the buffer size clearer * Use a builder to specify advanced options to create a ByteStream * Improved comments * Specify the unit to use for PathBodyBuilder.with_file_size * Improved comments following review * Rename PathBodyBuilder to FsBuilder * Renaming in FsBuilder - renames `with_buffer_size` to `buffer_size` - renames `with_file_size` to `file_size` - renames `byte_stream` to `build` * Make PathBody private * Updated API for FsBuilder * Document panic behavior of ByteStream::build * Document ByteStream::read_from * Move ByteStream::read_from No functional change * Update rust-runtime/aws-smithy-http/src/byte_stream.rs a -> an Co-authored-by: Russell Cohen <[email protected]> Co-authored-by: Russell Cohen <[email protected]>
* add: callback trait proposed in rfc#0012 add: callback setting API to ByteStream add: callback setting API to SdkBody add: callback tests for streaming and buffered data add: private callback fns for calculating checksums udpate: pub methods on private struct `Inner` to be private update: changelog remove: Sync bound from SdkBody test "sdk_body_is_send()" add: fn to merge `HeaderMap`s by appending add: tests for new functionality * add: Sync bound to callbacks refactor: poll_trailers method update: split out checksum callbacks into their own module formatting: use throwaway let binding instead of allow unused variable * add: license file to new crate add: readme file to new crate * add: missing anchor to Cargo.toml * rename: aws-smithy-checksum-callbacks to aws-smithy-checksums add: two more append_merge_header_maps tests update: make append_merge_header_maps pub(crate) remove: check for non-existent log line * remove: doc test for private fn * update: checksum callback struct names
This commit upgrades: * Kotlin to 1.6.20, * Kotest to 5.2.3, * Ktlint to 0.45.2; and * Jacoco to 0.8.8. Perhaps the only noteworthy change is that Ktlint now has a lint to detect that the name of a class/object defined solely in a file has to coincide with the filename.
* Update to remove usages of deprecated writers * Add Support for "debugMode" Add a `debugMode` flag. This will render a best-efforts `file:line` number comment for every generated section of code. * Fix server codegen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )