Partial Recover and Recoverf stack trace
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 990
- Forks
- 45
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
Both Recover and Recoverf helpers should build stack traces using debug.Stack() in order to print trace up to the panic line.
Contributor guide
No contributing guide indexed for this repository
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
Locate the Recover and Recoverf helpers and read how they currently build stack traces. Use the issue's debug.Stack() requirement as the completion check, verifying that each helper prints the trace up to the panic line and that the project's existing tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100