## Motivation and Context
Removes `CHANGELOG.next.toml` from `CODEOWNERS` since it no longer
exists. The file now lists the `.changelog` directory instead under
`Shared ownership`.
----
_By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice._
This PR fixes issues introduced by moving the repository from
awslabs/smithy-rs to smithy-lang/smithy-rs.
----
_By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice._
* A barely working code generation in typescript
* Extract shared socket into feature inside aws-smithy-http-server
* Building a fully functional application, I think
* Add NAPI build.rs
* Refactor all names to use typescript instead of js
* Add (hopefully) the PR bot for TS
* Clippy fixes
* Fix documentation
Signed-off-by: Daniele Ahmed <ahmeddan@amazon.de>
* set_reuse_port in socket not on windows
Signed-off-by: Daniele Ahmed <ahmeddan@amazon.de>
* Add example implementation
* Allow the new application to build
* Remove all occurrences of Python
* Simplify README
* Fix issue with the codegen-diff-revision script
* Try to prevent the ci-lint to bother us with TODO at this stage of development
* Remove codegen-client from typescript dependencies
Signed-off-by: Bigo <1781140+crisidev@users.noreply.github.com>
* Add CODEOWNERS and fix some other linting issues
* Add license
* Prevent from running tests on typescript in Windows
Signed-off-by: Bigo <1781140+crisidev@users.noreply.github.com>
* Initial work to remove error from this PR
* Update to call_async
Signed-off-by: Daniele Ahmed <ahmeddan@amazon.de>
* types/node in package.json
Signed-off-by: Daniele Ahmed <ahmeddan@amazon.de>
* Generate app.ts
Signed-off-by: Daniele Ahmed <ahmeddan@amazon.de>
* Improve makefile
* Adapting code to the latest changes and removing runtime dependency (for now).
* Removing rust-runtime/aws-smithy-http-server-typescript.
* Making CI happy.
* Restoring ServerCodegenDecorator to be like main.
* Adding back the aws-smithy-http-server-typescript crate back.
* Removing index.js file.
---------
Signed-off-by: Daniele Ahmed <ahmeddan@amazon.de>
Signed-off-by: Bigo <1781140+crisidev@users.noreply.github.com>
Co-authored-by: 82marbag <69267416+82marbag@users.noreply.github.com>
Co-authored-by: Alberto Pose <albepose@amazon.com>
* Move Python related folders to `@awslabs/smithy-rs-python-server` team
* Add `@awslabs/smithy-rs-server` team to Python related folders
Co-authored-by: Zelda Hessler <zhessler@amazon.com>
* Replace AtomicU64 with AtomicUsize to prevent compilation issues on 32 bits platforms.
* Make sure that Rust tests compile on MacOS.
* Add CHANGELOG next entry.
* Add a new CI job to check that smithy-rs compiles on 32bit Linux-based targets.
* No trailing commas pretty please.
* Point cross at the manifest explicitly.
* Skip crates with a Python dependency. Exercise all features.
* Install required dependencies.
* Do not fail fast, we want to see the result on all platforms.
* Set paths for both commands.
* Openssl must be installed inside the cross Docker container, not on the host machine.
* Fix connector setup if `rustls` feature is not enabled.
* Restrict feature set on powerpc.
* Pass openssl env variables to the cross Docker container
* Split in two commands.
* Enable debug level logs.
* Remove openssl feature (temporarily).
* Raise verbosity.
* Trigger CI
* `native-tls`, here we go again.
* Clean up.
* Trigger CI
* Trigger CI
* Add pkg-config.
* Change include path to include arch
* Trigger CI
* Allow workflow_dispatch on ci-pr to enable triggering this CI workflow from the GitHub web interface.
* Trigger CI? Why are you doing this to me GitHub?
* Trigger CI? Are you alive GitHub?
* Fix env variables for openssl
* Use features only for rust-runtime crates.
* Check all feature combinations for aws-smithy-client
* Dry-up env variables.
* A rogue `echo` was missing
* Feature-gate doc tests based on the features they require.
* Put .github folder under shared ownership.
* Fix docs.
* Fix feature selection for doctest.
* We are using methods that are only available if rustls is enabled - adjust feature gates accordingly.
* Remove workflow dispatch trigger.
This PR introduce a benchmarking tool that is run as part of the GitHub actions to allow to spot performance regressions in the server implementation.
The "deviation" between the last and current benchmark is posted as a message in the pull request.
I want to let this run for a little so we can figure out if GitHub action capacity can give us consistent results, otherwise we will have to move this to some capacity we own.
Co-authored-by: david-perez <d@vidp.dev>
ysaito1001