typelevel / typelevel/cats-effect-testing
Scalatest deadlocks very easily
Open
Nobody has claimed this yet.
bug
- Dominant language
- Scala
- Stars
- 194
- Forks
- 42
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 1
Description
Minimal example: https://scastie.scala-lang.org/NU86Wy4kTTukZzaSTUM2VA
I think this is because AsyncIOSpec passes scalatest's executionContext which is serialExecutionContext and not really suitable for general-purpose use.
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 the linked Scastie minimal example and inspect AsyncIOSpec, especially how scalatest's executionContext and serialExecutionContext are passed. Done means the minimal example no longer deadlocks under the affected integration, with behavior verified against an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100