Daniel Urban
Daniel Urban
My theory is that this is #3111, which was fixed in #3226 by overriding `race` in `Resource`. Which was fine, as long as `timeout` used `race`. However, since #4059 it...
@armanbilge > ...but because the fiber is incomplete, it will run the finalizer (ref.set(false)) when it completes (concurrently to the termination of the scope). Which I think is exactly the...
I don't think that modified `fromCompletableFuture` is necessary. This seems to work fine: `IO.fromCompletableFuture(...).onError(_ => IO.unit)`. The fact that an `.onError(_ => IO.unit)` changes behavior seems like a bug though....
@tpetillot `IO` doesn't use `defaultCont` (it has its own `cont`), so the first code you've linked doesn't run in this case.
No, that `f` in the code you link is the lambda passed to `handleErrorWith`, which does not throw a fatal (or otherwise) exception. The `.onError(_ => IO.unit)` thing "works", because...
@tpetillot I'm sorry, I don't understand you last sentence. In general, the approach in other (correct) cases is to detect the fatal error as soon as it occurs. An exception...
`sigaction` is documented to need `_POSIX_C_SOURCE`. And indeed `#define _POSIX_C_SOURCE 1` works on my machine (linux). We'll see what CI thinks about that (WIP PR: #4510). (I don't know what's...
Stacktraces broke at least on ARM Linux (scala-native; 2.13 and 3); 2 examples: - https://github.com/typelevel/cats-effect/actions/runs/18574362636/job/52958750712#step:22:1975 - https://github.com/typelevel/cats-effect/actions/runs/18574362636/job/52956834671#step:22:3670
> Do you think the errors in the log file have to do with 0.5.9 or with _Mumble_SOURCE? Which errors, in which log file?