CE have released their own take on tracing, with following notable changes compared to original ZIO Tracing:

• Instead of parsing lambdas, CE throws exceptions in IO constructors and cleans up stacktraces. That also means there is no regional control of tracing and AFAIK no way to avoid slight overhead even when tracing is completely disabled – but OTOH it may probably work on Scala.js
• Trace

Issue described in https://t.me/izumi_ru/3971

[info] Main Scala API documentation to /home/circleci/project/target/scala-2.13/api...
[error] /home/circleci/project/src/main/scala/com/ponv/Scenarios.scala:16:26: exception during macro expansion: 
[error] izumi.distage.model.exceptions.BadIdAnnotationException: Wrong annotation value, only constants are supported. Got: @izumi.distage.model

Is there a scala.js version? If not, can that be added?

For independent versioning, I think pulling out the integrations into separate modules may make sense. Otherwise they must all proceed in lock-step with every update to each library or to Scala.

I've implemented this for a couple of languages, but others are welcome too if you want to work on them. I'll keep a checklist here.

• Java, Scala (and other JVM languages)
• Rust (crates.io)
• JavaScript (npm)
• Haskell (Hackage)
• Elixir/Erlang (hex)
• Python (PyPI)
• C# (and other .NET lan

https://scalacenter.github.io/scalafix/docs/users/suppression.html

We should probably simply rename this annotation for more "zio-shield-ish" and make it specific, because we control the set of rules.

Redis api at times requires time values with different precision scales, rather than passing this cognitive load to the user for computing the correct long value each time, we can have base input type to be Duration instead.

Refer Keys#{migrate, restore, wait_}