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

Rust SDK Prototype Release #222

Open
Sushisource opened this issue Nov 15, 2021 · 9 comments
Open

Rust SDK Prototype Release #222

Sushisource opened this issue Nov 15, 2021 · 9 comments
Assignees
Labels
Rust SDK Issues about or asking for Rust SDK release

Comments

@Sushisource
Copy link
Member

We've had a number of people ask about Rust SDK progress. This issue serves for now as a place to track that progress.

Currently there is no official timeline for releasing a Rust SDK. However, I do plan to make the prototype SDK publicly exposed with no API compatibility guarantees. This issue will track that. It directly depends on #176

@bdbelevate
Copy link

Any thoughts on this? I can see you guys are working on it, but if there's a specific timeline to it or ways that we can help contribute, let me know. Thanks!

@Sushisource
Copy link
Member Author

Any thoughts on this? I can see you guys are working on it, but if there's a specific timeline to it or ways that we can help contribute, let me know. Thanks!

Still no timelines around official release. However, if your question is more "can you just publish this to crates.io?" then yes, I can prioritize that so at least it's a bit easier to use, if still alpha.

@bdbelevate
Copy link

Thanks for the update. I don't mind forking and keeping our own version to use locally or within our own cargo workspace. But in trying to us it, what I do see is that it seems as if the rust SDK has no way to send a response to temporal for a workflow. I don't see any tests where this happens and it also seems like the exit for a workflow must be WorkflowResult<()>. I'm not sure if this is intentional or just upcoming changes. Maybe I'm missing something but it appears the typescript sdk gets around this by sending it's own grpc result.

@Sushisource
Copy link
Member Author

That's correct. The workflow authoring APIs in general are still very rudimentary in the Rust SDK. The underlying functionality is there (that's what typescript uses), it's just not all exposed yet.

We'll want to publish a proposal to our proposals repo to get some ideas around what we want a final workflow API to look like in the Rust SDK before putting in the work to polish it up. It'll definitely happen but other things are higher priority right now.

There seems to be enough demand generally that getting discussions going around that proposal might at least be good to get started though. So, I'll see about finding some time for that and will update here with anything relevant.

@bdbelevate
Copy link

Thanks - that would be awesome. Like I mentioned our team would be happy to help contribute once there's a proposal.

@Sushisource Sushisource added the Rust SDK Issues about or asking for Rust SDK release label Feb 1, 2023
@Sushisource
Copy link
Member Author

I forgot to mention in this issue that the first draft of the workflow api is here #550

@mkarbo
Copy link

mkarbo commented Apr 3, 2024

Hello! I was just wondering if anything has changed on your side regarding commitment to a stable SDK release for rust?

We're totally onboard with the fact that it is not yet priority and not committed, and are just wondering if anything has changed since Jan 8 and Dec 5 (last activity on #550)? 😄

Hoping that I will be able to use it sometime in the near future from our favorite language! 🦀

@Sushisource
Copy link
Member Author

@mkarbo Not yet on the docket. We will definitely keep everyone here posted, and in community slack, once we begin :)

@mkarbo
Copy link

mkarbo commented Apr 3, 2024

Alright! Thanks for the update :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rust SDK Issues about or asking for Rust SDK release
Projects
None yet
Development

No branches or pull requests

3 participants