FreeT is stack-unsafe
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 5.5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
...somehow.
at cats.free.FreeT.$anonfun$step$1(FreeT.scala:163)
at scala.Function1.$anonfun$andThen$1(Function1.scala:85)
at cats.free.FreeT.$anonfun$step$1(FreeT.scala:163)
at scala.Function1.$anonfun$andThen$1(Function1.scala:85)
at cats.free.FreeT.$anonfun$step$1(FreeT.scala:163)
at scala.Function1.$anonfun$andThen$1(Function1.scala:85)
at cats.free.FreeT.$anonfun$step$1(FreeT.scala:163)
at scala.Function1.$anonfun$andThen$1(Function1.scala:85)
at cats.free.FreeT.$anonfun$step$1(FreeT.scala:163)
at scala.Function1.$anonfun$andThen$1(Function1.scala:85)
at cats.free.FreeT.$anonfun$step$1(FreeT.scala:163)
at scala.Function1.$anonfun$andThen$1(Function1.scala:85)
That goes on for a while and turns into an SOE. Staring at the source code, it looks like a recursive flatMap is causing it, but it's hard to say exactly.
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 cats.free.FreeT.scala around line 163 and reproduce the reported stack overflow, focusing on the repeated step and flatMap-related calls in the trace. The issue does not identify a test or a precise reproduction, so first determine the triggering operation; done means the reported recursion no longer overflows the stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100