Stream does not complete on ROLLBACK_FAILED
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- aws, javascript
- Domain
- cloud
Research direction
Start at line 83, where stack operation statuses are checked, and compare the handling of ROLLBACK_FAILED with the existing completion condition. Update the condition so a failed rollback ends the stream as completed, then verify that the stream terminates for this status.
Written by the indexing model from the issue text.
Description
When a stack operation fails and the rollback fails as well, the stream should end be completed.
Thus, in line 83 I think you should check for ROLLBACK_FAILED too.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
More from mapbox/cfn-stack-event-stream
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
assembly-line
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Fix tests Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
All issues in mapbox/cfn-stack-event-stream
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·