-
Notifications
You must be signed in to change notification settings - Fork 52
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
beacon is dead after network error #108
Comments
I would like to revive this issue and discuss possible solutions to this issue.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have the following scenario on which there is a network problem during beacon setup, where I get the following exception inside ZBeacon:
The problem is that the caller cannot know it happened as the exception was triggered inside ZActor which has it's own thread (using Threading package).
The text was updated successfully, but these errors were encountered: