SubroutineInput - StartOverOnRetry flag
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- C#
- Stars
- 334
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
- Current behavior is that Forge will remember the CurrentTreeNode of the Subroutine and visit that node on failover/retry.
- What if the user would like to start from the RootTreeNode on retry?
- I could see either behavior making sense, so we should add a property flag in SubroutineInput to determine the desired behavior.
- Probably would need to delete all the state from subroutine session before retrying. I don't want to parse through the data though, so perhaps just starting a brand new subroutine SessionId would suffice.
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 with SubroutineInput and the failover/retry handling that restores CurrentTreeNode or could return to RootTreeNode. Clarify the flag's behavior and whether retrying should create a new subroutine SessionId; done means the selected retry start point and session-state behavior are implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100