Repository navigation
Conversation
Brings in temporalio/sdk-rust#1640. Ran core:update's tool and cargo fetch, and regenerated the protos Core's API update changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What was changed
Updates the sdk-core submodule from
38f83151to212e8150, Core's currentmain, which includes temporalio/sdk-rust#1640.update-coretool (whatrake core:updateruns), which imported Core's changelog entries as fragments, thencargo fetch(oneCargo.lockline).rake proto:generate: Core's range includes an API update (Update Upstream Protos for Nexus Handler Callbacks sdk-rust#1652), which changes 10 protos' generated Ruby, RBI and RBS files.Why?
temporalio/sdk-rust#1640 fixes workers losing workflow tasks while a workflow waits on a local activity ("Trying to send a new WFT for a run which already has one!"). The lost workflow task times out, and the retry can fail with a nondeterminism error and leave the workflow stuck.
Noticing this during load testing.
Checklist
Closes
How was this tested:
cargo check --locked, Ruby 3.3).Any docs updates needed?
No.
🤖 Generated with Claude Code