Skip to content
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

Aborting callOnEachEvent #114

Open
palaga opened this issue Oct 22, 2024 · 0 comments
Open

Aborting callOnEachEvent #114

palaga opened this issue Oct 22, 2024 · 0 comments

Comments

@palaga
Copy link
Contributor

palaga commented Oct 22, 2024

Currently, a call to callOnEachEvent can't be aborted. If some higher level logic is restarted, a new event loop will be created, but an old one cannot be cleaned up (i.e. aborted).

My use case is a custom node in node-red. A redeploy of the node causes a new event loop to be spawned.

A solution could be to let callOnEachEvent return an object that can be aborted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant