temporalio / temporalio/features
[Feature Request] Unknown SDK flag should behave consistently across SDK
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.
If the SDK encounters an unknown SDK flag on replay, often due to downgrading an SDK, SDKs should behave consistently. Currently the SDKs behave differently:
- Fail the workflow task (Go and Java)
- Ignore the unknown flag (Core)
Originally when we added SDK flags we said the SDK should fail on an unknown flag. Ignoring the unknown flag makes it easier to roll back an SDK, but also puts the workflow into an inconsistent state.
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 tracing how unknown SDK flags are handled during replay in the Go and Java SDKs, then compare that behavior with Core. The work is done when all SDKs consistently follow the intended unknown-flag behavior and compatibility coverage verifies it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100