-
Notifications
You must be signed in to change notification settings - Fork 820
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
Add Rust SDK async/await syntax support and minor improvements #1733
Conversation
/assign @EricFortin |
Build Succeeded 👏 Build Id: be9f9fe3-b1d9-4f51-96e0-6d20d27b208f The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Failed 😱 Build Id: f1c9ed8d-4471-4066-a4f0-78132ea314dd To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
As a side note
Which is tracked under gohugoio/hugo#7293 . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, just would like clarification on std-async vs tokio -- we probably don't want to tie ourselves to one of the other 😬 ?
error-chain = "0.11.0" | ||
grpcio = "0.6.0" | ||
protobuf = "2.16.2" | ||
futures = { version = "0.3", features = ["compat"] } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In theory, this should work with either tokio or std-async, yeah?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's right.
run-sdk-conformance-test is working with async-std.
I've tried the sample that works with tokio in the following branch and confirmed that it works.
Should I commit such an example to this PR?
https://github.com/yoshd/agones/blob/a740ed653b72ed3d1a05accbf790f076af991090/examples/rust-async-simple/src/main.rs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I don't think so - just wanted to make sure 👍
Sounds like this is good to go 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do it!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, yoshd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: 049e634d-7de9-4f29-aa2e-6c8cda4debce The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
…eforgames#1733) * Add Rust SDK async/await syntax support and minor improvements * Fix comment in run-sdk-conformance-test-rust Co-authored-by: Mark Mandel <[email protected]>
What type of PR is this?
/kind feature
What this PR does / Why we need it:
Added functions that supports async/await syntax.
The existing API can be used as it is without breaking it.
This allows the following asynchronous calls:
Also, in order to resolve #1201, I fixed grpcio's openssl feature to allow it to pass through.
I updated the Rust edition to 2018 and also updated the other dependent crate versions.
Other minor cleanups have also been done so that warnings will no longer appear at build time.
Which issue(s) this PR fixes:
Fixes #1732, #1201
Relates to #1300