Daniel Urban

I've tried setting up building a fat JAR on this branch: https://github.com/durban/choam/tree/lc307 A fat JAR can be built like this: ``` git clone https://github.com/durban/choam.git cd choam git checkout 8bbe6475 #...

Okay, I've tried with `TestControl.executeEmbed`. Honestly, I've expected much "fairer", because of what @djspiewak says. But still, with the test runtime it's better than with the real one. This is...

For `Spawn[IO]`, would this return `availableProcessors()` or the size of the WSTP? (Because the two is not necessarily the same.)

In that case, I can't really see how to implement it as a `: Int`... return the size of *what* WSTP? There might not even exist one. (While if we're...

I think I don't understand this any more. I thought that the difference is not to call shutdown hooks. But I'm now trying to find shutdown hooks, and we only...

Yeah, SIGTERM is handled directly with signals: https://github.com/typelevel/cats-effect/blob/series/3.x/core/native/src/main/scala/cats/effect/Signal.scala

Yeah, maybe. Although I don't think it's _wrong_ to call `_exit`. But I don't think the test in #4428 is testing anything useful (at least on scala-native).

Okay, I think I can turn on and off the (probably) segfaults with a scala-native config flag :grinning: ``` generateFunctionSourcePositions(true) // ioAppTestsNative fails in CI, and locally I get incorrect...

Current status: - `generateFunctionSourcePositions(true)` makes `ioAppTestsNative` fail on `ubuntu-22.04-arm` (I think, although lately I haven't seen it) and `macos-14` (definitely). I believe both of those are ARM64. With `false`, everything...

Forgot to write a status update here: I've fixed something in scala-native/scala-native/pull/4301, which fixes the incorrect exception stacktraces for me locally. I guess we'll see if it fixes the segfaults...