You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening an issue to investigate a bug from @GreyXor, shared in #45.
I have two services, Config and Event. Where Event is a dependency of Config.
typeConfigServicestruct {
Event*event.Service
}
In my Config's shutdown method, I calling anEvent's method.
With v2.0.0-beta.3, it's working as expected because the actual reverse order is respected.
With v2.0.0-beta.5, it's randomly not working because Event is randomly Shutdown before Config. (because of the async)
@GreyXor I was not able to replicate this bug. Can you write a demo?
FYI, I just added a commit to v2 for supporting shutdown on circular dependencies.
The text was updated successfully, but these errors were encountered:
I'm opening an issue to investigate a bug from @GreyXor, shared in #45.
I have two services,
Config
andEvent
. WhereEvent
is a dependency ofConfig
.In my
Config
's shutdown method, I calling anEvent
's method.With
v2.0.0-beta.3
, it's working as expected because the actual reverse order is respected.With
v2.0.0-beta.5
, it's randomly not working becauseEvent
is randomlyShutdown
beforeConfig
. (because of the async)@GreyXor I was not able to replicate this bug. Can you write a demo?
FYI, I just added a commit to v2 for supporting shutdown on circular dependencies.
The text was updated successfully, but these errors were encountered: