BREAKING: Add retryable arg to stage decorator
@jmgate is already working on this.
Since Sep 5, 2024.
Assessment
This issue has not been assessed yet.
Description
It's a bit of a learning curve for those trying to create bare-bones staged scripts to see all those retry command line arguments automatically populated when they haven't designed their stages to be retryable. A better user experience would be to add a retryable flag to the stage() decorator and default it to False. Only if True do all those retry arguments get generated.
Note: This will be a breaking change.
- Dominant language
- Python
- Stars
- 23
- Forks
- 2
- 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 sandialabs/staged-script
-
Quick Type: Refactor
Difficulty 3/5 1-2 days Newbie friendliness 35/100
sandialabs/staged-script#300 · 1 comment ·
-
Type: Feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sandialabs/staged-script#172 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
sandialabs/staged-script#139 ·
-
Type: Documentation
sandialabs/staged-script#98 · 1 comment · 1 assignee ·
-
Type: Feature
sandialabs/staged-script#97 · 1 assignee ·
All issues in sandialabs/staged-script
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100