Create Warning Fiber In Test Clock Scope

[adamgfraser]

Resolves zio/zio-http#1896.

Currently in the TestClock we fork a warning fiber when a caller accesses the time that we interrupt when the caller actually adjusts the time or when the scope of the TestClock is closed.

However, this can create an issue if the warning fiber is forked in an inner scope where for example it uses an executor that is not valid outside that scope and the fiber is interrupted when the TestClock scope is closed after the inner scope is closed.

We can prevent this by forking the fiber at the time that the TestClock layer is constructed and merely completing a promise when we want to "start" the warning. This way we can ensure that the fiber is forked in a scope that is still valid when the fiber is finalized.

[frekw]

Wow, tricky! Great work @adamgfraser 🙏

[frekw]

Amazing, hopefully we can now we full ZIO 2.x support in Caliban (by updating zio-http). I'm really excited by that – do you know if there's currently an ETA for 2.0.7 (since 2.0.6 was ~3 weeks ago and there have been some bug fixes and performance improvements since 😃)?

[ghostdogpr]

@frekw can you test our branch with the zio snapshot that will be created very soon? So we are 100% sure it's okay before a release 😄

[frekw]

@ghostdogpr haha I'm already sitting and impatiently following the CI run 😂

[frekw]

Aww CI seems to be failing so no snapshot was published :/

[frekw]

@ghostdogpr works great! 🎉 🎉 🎉

  + ZHttpAdapterSpec
    + http
      + test http endpoint
      + test interceptor failure
      + lower-case content-type header
    + test ws endpoint
      + legacy ws
      + graphql-ws
5 tests passed. 0 tests failed. 0 tests ignored.

Executed in 12 s 250 ms

[info] Completed tests
[success] Total time: 32 s, completed 6 Feb 2023, 15:40:38