-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically starting NervesHubLink.Supervisor race condition #11
Comments
A few things:
|
I think one way we could address this issue is by allowing the library to start its own supervision, or be included manually in external supervision. Much like how |
With the It's not perfect by any means, and I'd be happy to look into this if this feature is still wanted, but as its been 3.5 years since any activity on this issue, I think its best to close it for the time being. |
In the switch from NervesHub to NervesHubLink the
NervesHubLink.Supervisor
is automatically started on boot instead of "whenever I want to start it". This change has introduced a race condition in my code because myNervesHubLink.Client
relies on a process that may not have been started yet. Obviously I can catch the exception and reschedule the update but I'm wondering why the change?This change also takes away the ability to conditionally include the supervisor which is something I do in development all the time when I'm testing without pushing releases.
The text was updated successfully, but these errors were encountered: