temporalio / temporalio/sdk-ruby
[Feature Request] Test randomness seed update over reset
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 204
- Forks
- 42
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 28
Description
Describe the solution you'd like
Add a test that will confirm post-reset-point workflows have a different update seed. Probably by running a workflow to completion that uses randomness to get some value into history twice (e.g. as two activities with random-built inputs), then reset the workflow between those two points and run it to completion. Then confirm the value pre-reset is the same but different post-reset.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing workflow reset tests and the randomness-seed entry point in the Ruby SDK. Add coverage for running a workflow, resetting it, and completing it again; verify the value before reset is unchanged while the post-reset value differs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100