Display what to do next when a job fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the CLI output path used when a job fails and trace how the failed job identifier is available there. Add a next-step message showing the tilesets job command with the relevant tileset and job identifiers, then verify that failed jobs display actionable debugging guidance.
Written by the indexing model from the issue text.
Description
If a job fails, it would be nice if there was some text describing what you should do to debug
Something like
Run
tilesets job tristen.transit-v1 ckcc6rwqz001j08lbdwrnhygrto learn more.
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- 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/tilesets-cli
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
mapbox/tilesets-cli#217 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapbox/tilesets-cli#216 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mapbox/tilesets-cli#193 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
mapbox/tilesets-cli#190 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapbox/tilesets-cli#171 · 1 reaction ·
All issues in mapbox/tilesets-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100