Paul S.

Hi guys. I've just noticed that this breaks `classgraph` on JDK 10: https://github.com/classgraph/classgraph/issues/255 Could you fix that? Pleeeease?

Guys, instead of using username you may just take a prefixed hash. Like `user-${mummur128(creds)`. It would fix both the parsing and the credentials leak issues.

Hi, I guess this issue had been created semi-automatically. izumi does not depend on zio directly, it has BIO, a TF abstraction layer. Izumi also works with monix and cats-effect....

Nope, it's a separate story. It may be a discussable but usable complementation for #306 but it's not smth urgent.

At the moment the problem is solved with several additional planner phases. Most likely we don't need fullscale replanning capabilities.

> Expected failure with missing tag, not a `type lambda` failure. This case is fixed in `izumi-reflect` 1.1.4-SNAPSHOT > Injector should fail without implicit Tag[N#TPE] This has to be fixed...

@neko-kai : seems like we have two issues. `make` emits some code which incorrectly tries to combine tag for a proper type with an empty arg list. And reflect fails...

This seems to be specific for a JUL bridge, so, this, probably, should only be addressed in the docs.

log4j -> slf4j adapter works fine

First example is not a bug. `make[LogMessages[F]]` should be erased in favour of `many[PonvScenario[F]].ref[LogMessages[F]].tagged(Mode.Test)` thus `.ref[LogMessages[F]]` gets invalidated. It looks weird but it's a sound behavior. We may try to...