Vasil Vasilev

Settings: ```scala enablePlugins(SonatypeCiReleasePlugin) ThisBuild / spiewakMainBranches := Seq("main") ThisBuild / spiewakCiReleaseSnapshots := true ThisBuild / publishSnapshotsAsHashReleases := true ThisBuild / spiewakCiReleaseTags := true ``` Output: ```yaml publish: name: Publish Artifacts...

Settings: ```scala enablePlugins(SonatypeCiReleasePlugin) ThisBuild / spiewakMainBranches := Seq("main") ThisBuild / spiewakCiReleaseTags := true ``` Output: ```yaml publish: name: Publish Artifacts needs: [build] if: github.event_name != 'pull_request' && (startsWith(github.ref, 'refs/tags/v')) strategy:...

@iravid #1538.

So for your usecase, it's enough if you just modify the units per interval?

Externally means, the stream elements have no effect on it, i.e. it doesn't depend on the stream elements?

Another idea I have is to try and merge `suspended` (`AtomicBoolean#value`) with `IOFiber#outcome`. `AtomicBoolean` is a bit of a deceptive class. It doesn't actually offer any optimization when compared to...

For what it's worth, I'm a maintainer of `sbt-jcstress`, we could update it, not sure how much work that will require. I believe it is quite out of date now.

That's great! I did not know that 🤣

To avoid setting high expectations, the branch that Daniel has linked to above is a very stupid implementation where every "schedule a fiber on a thread pool" operation (including resuming...

This error looks similar to the error when the old Scala compilers are executed with newer JDK versions (9+) that do not have a proper `rt.jar`. Sbt has solved this...