Lifecycle.fromZIO can include this as a workaround... (Although, this is reproducible in plain Lifecycle and cats Resource too, as long as ZIO fork is used, so maybe no)
This feels like a gotcha in zio, because I suppose it is quite common to use
forkManaged.
Hi! I'm trying to improve the logging in my project and make LogStage work with GCL structured logging.
Right now, my log is setup like this:
make[LogIO2[IO]].from(LogIO2.fromLogger[IO] _)I'm also using distage-extension-config and have in my application.conf
logger {
levels {
...
}
json = false
}1) Is there any docs about this special config that seems to affect the logging?
If is set json = true I do get json output. However, to make it work with GCL I would need to change the json a bit.
For example, in the logstage json there is meta.level: "debug" and GCL needs severity: "DEBUG".
2) How can I configure the json output?
LogstageCirceRenderingPolicy seems like the correct solution. It is quite nice. Also need to make sure other stuff gets routed through my logger.The
loggerconfig is still somewhat of a mystery to me, and how to make sure my logger is used by distage (some other loggers defined in LogAppBootModule).
@Edvin-san
There's no documentation for that config, but the case class being read is the following SimpleLoggerConfigurator.SinksConfig (example usage) and the component responsible for reading the config is the SimpleLoggerConfigurator there.
and how to make sure my logger is used by distage (some other loggers defined in LogAppBootModule).
You may override make[IzLogger] instead of LogIO2 - this will affect the LogIO1/2 etc. automatically since they depend on IzLogger themselves. User bindings override any default / builtin modules, so no additional steps are required beyond just defining a component in your own plugins.
The loggerconfig is still somewhat of a mystery to me
Yeah, it's a function that got somewhat forgotten, it does need to be documented and untied from distage in the future (so that users of logstage-core-only can use it too)
SIGTERM it starts shutting down (I can see AppShutdownStrategy "Going to shut down..." in logs).I can also see http4s PoolManager "Shutting down connection pool". But then it just sits there. Do you have any recommendation on how to debug this in distage? Can I see which resource is causing the problem?
One thing that could help is placing a breakpoint on this line or adjacent.
finalizers contains all the finalizers in order and f variable may contain some information about the finalizer, like type name, so you could possibly track which one is the last by resuming at this breakpoint.
zio.internal.FiberContext) has a synthetic stacktrace that is accessible from the heap that can tell the history of computations – there's also a zio.Fiber.dump function and zio-zmx project that is supposed to provide an ability to dump global fiber state more easily.
type PositiveInt <: Int and an Int, and it all works fine in Scala 2.13. Looking towards the dotty future, I've tried to make a pr that 'works' for my use case in Scala3 but I'm a bit lost in the inheritance macros. Can someone help me out a little plz?
Has type in ZIO and I have this:object data {
type Data[A] = Has[DataValue[A]]
final case class DataValue[A](value: A)
object Data {
def apply[A: Tag](value: A): Data[A] = Has(DataValue(value))
def get[R,A]:(f:R => A):A = ???
}
Is there a way I can do the following wiring:
A have an interface A that is implemented in several places and wired as follows
many[A].add(...)Then in 2 places I depend on the aggregate of them:
many[B].from((aSet: Set[A]) => new B(aSet))
// Here I do not depend on all As, but only on a subset of them
many[C].from((aSubset: Set[A]) => new B(aSubset))Is there a way (maybe tagged) when building the many[A] to add some sort of tag/group to it and then to fetch the dependency (aSubset: Set[A]) from that tag/group ?
A and just do it inside the from method. But let’s say that’s not possible in my setup
// build subset
many[A].named("subset").add(...)
// add subset to full set
many[A].refSet[A]("subset")
// use full set
many[B].from((aSet: Set[A]) => new B(aSet))
// use subset
many[C].from((aSubset: Set[A] @Id("subset") => new B(aSubset))addSet/refSet/weakSet methods, even though you cannot extract a smaller set from a bigger set (other than directly at value level like make[Set[B]].from((_: Set[A]).collect { case b: B => b}))
tagged to mark elements that should be in the set at different configurations - but they won't be able to exist all at the same time, different configurations will choose different elements in a mutually exclusive way (see 'Changes in Activation behavior' section in 1.0 release notes: https://github.com/7mind/izumi/releases/tag/v1.0.0), so that's an unrelated instrument, but I think refSet above should work well for your usecase
Has-like methods like this https://scastie.scala-lang.org/Xg6LV87fT5aMEUdELvQGAw
@neko-kai It does work what you suggested, but I get the following error:
app Caused by: izumi.distage.model.exceptions.MissingRefException: Proxy for {type.scala.collection.immutable.Set[=A]} is not yet initializedThis is due to the fact that I have something like:
make[C].from((aSet: Set[A]) => new C(aSet.toList))Since class C requires a List[A]. It seems that in the moment when that line is executed, the set is not yet fully initialzed. If I change C to require a Set[A] it works, but it is not what I want
C itself included into Set[A] - perhaps transitively? That's the only thing that would cause a proxy to be generated to allow a cyclic dependency to still work. You may try to print or inspect your wiring data to locate the cycle (https://izumi.7mind.io/distage/debugging#pretty-printing-plans, https://izumi.7mind.io/distage/debugging#graphviz-rendering ) but if it's deliberate than you'd pretty much have to use a lazy constructor
Hi, just wanted to say that the new distage 1.0.4 version seems to have fixed my shutdown issues :thumbsup:
Hi! I think I may have a problem with resources not being cleaned up. When my app receives
SIGTERMit starts shutting down (I can see AppShutdownStrategy "Going to shut down..." in logs).
I can also see http4s PoolManager "Shutting down connection pool". But then it just sits there. Do you have any recommendation on how to debug this in distage? Can I see which resource is causing the problem?
Tag)
tag.tag quite a bit. Still good to have since it's less work for the compiler. Not a big issue
def x[F[_]: TagK, A: Tag]: Tag[F[A]] = Tag[F[A]]But LTag will break on that. You can also summon "weak" versions using
WeakTag[A]/LTag.Weak[A] - these will not attempt to resolve type parameters using tag evidence but will just include unresolved type parameters as written, e.g. def x[A] = WeakTag[A]; x[Int] = literal WeakTag[A], not WeakTag[Int]