Skip to content

EventHandler is not properly restarted after a watcher disconnection #630

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

Closed
metacosm opened this issue Oct 27, 2021 · 0 comments
Closed
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@metacosm
Copy link
Collaborator

When an error occurs that leads to watchers being closed, we also close the event handler so that events are not processed anymore. However, when we attempt a reconnection, we don't currently have any means to restart the event handler resulting in events not being processed anymore after a disconnection occurs.

@metacosm metacosm added the kind/bug Categorizes issue or PR as related to a bug. label Oct 27, 2021
@metacosm metacosm self-assigned this Oct 27, 2021
adam-sandor pushed a commit that referenced this issue Oct 28, 2021
Properly start event handler when starting the event source. 
Minor clean-ups.
Fixes #630
Co-authored-by: csviri <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant