temporalio / temporalio/features
Provide user access to randomness seed and changes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
There are several scenarios where a user may want to create distinct random number sequences. For instance, telemetry may need random numbers but the addition or removal of telemetry shouldn't change any randomness uses in the workflow itself. In particular when such things are done under the hood as part of plugins.
Describe the solution you'd like
Provide a way to get the initial randomness seed as well as notification of changes. If possible, providing an implementation of Random or equivalent which reseeds itself would be good.
Additional context
Per-SDK Tickets
- Go -
- Java -
- TypeScript -
- Python - https://github.com/temporalio/sdk-python/issues/1319
- .NET -
- Ruby -
- Rust -
- PHP -
- Temporal CLI -
Contributor guide
No contributing guide indexed for this repository
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 reviewing the feature request and the linked Python SDK ticket, then compare the unchecked per-SDK entries to determine the intended scope for each SDK. Done would require an agreed way for users to access the initial randomness seed and receive notifications when it changes, with SDK-specific work tracked in the listed tickets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, ruby, rust, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100