-
-
Couldn't load subscription status.
- Fork 7.3k
[rust-server] Update to hyper1 in rust-server generator #21422
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
Conversation
…e to rust-server generator
|
thanks for the pr all tests passed cc @frol (2017/07) @farcaller (2017/08) @richardwhiuk (2019/07) @paladinzh (2020/05) @jacob-pro (2022/10) |
56bda8e to
51b9a59
Compare
* Add tests to all examples, clippy, tests, cli-bin, run examples * Use headers Auth structs * Fixup various clippy lints * Move more Service impl to use BoxBody * Reduce generic restriction on some Service impl where possible
51b9a59 to
195f159
Compare
|
@wing328 Thanks for the initial pass. I've now tested this in our server stack and made a few tweaks with various bugs I have found. |
|
thanks for the PR let's give it a try |
Following on from #21332 this PR completes the upgrade to Hyper1.
Plus all of the changes from #21332
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master(upcoming7.x.0minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)Leaving this as draft for now, I'm running some testing of it through to us using it in production staging environments to validate the changes.