zio | platform abstract/virtual filesystem framework | File Utils library

You can use ZIO.collectAll to convert List[Task] to Task[List], I thought it was ZIO.sequence..., maybe I'm getting confused with cats...

Following example works with Zio2

As it turns out, all the ATA commands need to be in 8 bit (or 1 byte) input/output. This means that all the inw() and outw() function calls should be converted into inb() and outb() function calls instead. When I made the switch, the problems disappeared!

Undressed stmN: STM[TInt] and now it's simply n: Tint and being tracked as a constructor parameter. This requires construction of the Client to be pulled into, effectively, a TRef.map:

This is expected behavior and doesn't have anything to do with ZIO Test or the Clock.

Interruption in ZIO does not return until the effect has been successfully interrupted, which is an important guarantee for resource safety. In wait(5).race(wait(15)), wait(5) wins the race after 5 seconds. At that point race attempts to interrupt wait(15). However, interruption normally occurs "between" effects and wait(15) is a single block of side effecting code so there is no way to safely interrupt it in general. As a result, interruption suspends until wait(15) has completed execution, but by this time 15 seconds have elapsed and the test has already timed out.

If you don't want to wait for interruption to complete you can use the disconnect operator, for example wait(5).race(wait(15).disconnect). With this change your test will pass as written. You can also use the attemptBlockingInterrupt to direct the ZIO runtime to attempt to interrupt a single block of side effecting code like this by interrupting the underlying thread, though this is relatively heavyweight.

TL;DR: this is not possible yet as some of the code you are using rely on macros and is not yet published for Scala3.

SBT plugins runs with Scala 2.12 no matter which Scala version is used in your project, thus you don't have to try to use plugins with _2.13 or _3 suffix, just use the regular syntax that will actually pick _2.12 artifacts.

That is, in plugins.sbt:

U stands for “unexceptional” as in it isn’t expected to produce exceptions in the error channel (thus the Nothing In the error channel of the underlying ZIO).

R stands for “Resource” or “Requirement”. I personally prefer to think of it as the latter because it fits better with my mental model of not being able to run an effect until all the requirements are satisfies.

I'm not familiar with ZIO, there might be a built-in way to achieve the same.

I would go with something like the following:

After looking at the source code I have figured it out:

You should wrap your Java service with callback in an effect using effectAsync: