Mismatch in `workflow_id_reuse_policy` across testing and production environments
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start at lib/temporal/testing/temporal_override.rb around line 83 and compare its workflow_id_reuse_policy default with the production behavior described in the issue. Reproduce the mismatch in the Temporal testing environment and inspect relevant tests; done when the intended default is established and testing behavior is aligned or clearly documented.
Written by the indexing model from the issue text.
Description
When executing Temporal tests locally, workflows with the same workflow_id, and COMPLETED status are not rerun. They raise a WorkflowExecutionAlreadyStartedFailure.
But this is not the case in production, where COMPLETED workflows with the same workflow_id are rerun without passing {workflow_id_reuse_policy: :allow} explicitly.
I have currently patched https://github.com/coinbase/temporal-ruby/blob/b5efd2cef802be2fa97d5bab04839413726ac06e/lib/temporal/testing/temporal_override.rb#L83, to use :allow as the default value.
Is this intended behavior ? I feel the testing environment should be as close as possible to dev & production.
- Dominant language
- Ruby
- Stars
- 287
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from coinbase/temporal-ruby
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
coinbase/temporal-ruby#361 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
coinbase/temporal-ruby#328 · 1 comment ·
-
NoMethodError when await_workflow_result is called for long running workflowsPossibly taken @iekundayo claimed this 717 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
coinbase/temporal-ruby#326 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
coinbase/temporal-ruby#324 · 3 comments · 2 reactions ·
-
Unable to reset workflow due to the inability to resolve Temporal::ResetReapplyTypePossibly taken @lawrencewong claimed this 718 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
coinbase/temporal-ruby#322 ·
All issues in coinbase/temporal-ruby
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
TheOdinProject/curriculum#31479 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
taskcluster/taskcluster#9284 · 1 comment ·
Maintainers usually reply within 1 day
-
Class option relations are appended to the command on every runPossibly taken @auraseb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100