re-enable stack traces, maybe?
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 175
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
SkunkException extends NoStackTrace because IO stacktraces have always been nonsense, but cats-effect 2.2 changes this. See how it looks with stack traces enabled and maybe turn them on?
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 by inspecting SkunkException and its NoStackTrace behavior, then compare it with cats-effect 2.2 when stack traces are enabled. Verify whether the resulting traces are useful for Skunk failures; done means reaching a clear decision about enabling them and documenting the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100