cats-effect
cats-effect copied to clipboard
typelevel
The pure asynchronous runtime for Scala
Seems to happen much more often in CI. I have yet to reproduce locally. Example output: ``` [error] sbt.ForkMain$ForkError: java.lang.NullPointerException: null [error] at org.specs2.reporter.TextPrinter.printSkipped(TextPrinter.scala:181) [error] at org.specs2.reporter.TextPrinter.printSkipped$(TextPrinter.scala:178) [error] at org.specs2.reporter.TextPrinter$.printSkipped(TextPrinter.scala:292)...
The current Dispatcher suffers from the following problems : * algebraic product components of the effect are lost at the point of dispatch (WriterT's log) * algebraic coproduct components (EitherT,...
The following code always hangs: ```scala import cats.effect.unsafe.{IORuntime, IORuntimeConfig, Scheduler} import cats.effect.{IO, Resource, Sync} object App extends App { locally { lazy val newRuntime: IORuntime = IORuntime.apply(cpuPool, cpuPool, Scheduler.createDefaultScheduler()._1, ()...
Following an extensive [discord discussion](https://discord.com/channels/632277896739946517/632278585700384799/986295968389562418), it seems we can be better at teaching the program-as-values paradigm in the Cats Effect documentation, and that this should be given priority over concurrency...
The following PR tries to fix #2610 I'm not really sure what I'm doing here 😅 if this is utter garbage please feel free to close it. As I've understood...
Fixes https://github.com/typelevel/cats-effect/issues/2983 ... but breaks the laws 😕
Would there be any interest in folding the features of [cats-retry](https://github.com/cb372/cats-retry) (i.e. a few combinators for retrying effectful actions + a DSL for building retry policies) into CE 3? Would...
Probably related to #2580. It's usually much more useful to have fiber dumps during unit testing, but the current solution is baked into `IOApp`. We need to find a composable...
It's important to convince ourselves that we haven't somehow entirely destroyed performance on scalajs. The benchmark results are *really* inconsistent and it would be immensely helpful if someone who understands...
Here, we can track the progress of major libraries upgrading to CE3. That should be a nice way of finding out whether any of them are going to be late...
