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

An observing service can bring down an acting service, only if the acting service's logic is added via a plugin. #86

Open
jimimatrix opened this issue May 8, 2017 · 0 comments

Comments

@jimimatrix
Copy link

jimimatrix commented May 8, 2017

I found an odd scenario: an observing service can crash and bring down an 'acting' service, but only when the acting service's logic is added via a plugin. In the following code, and observing service sets up {model: observe} for a pin. 2 different acting services (actor-with-plugin.js and actor-without-plugin.js) run the same 'seneca.act' code, but one does so as a plugin and the other does not. When observer.js throws an error, actor-with-plugin.js crashes, but actor-without-plugin.js does not. I would not have expected that an error in the observer would bring down an acting service. Even more bizarre is that the acting service cares that there is an observer at all! (ie I expect {model: observe} to be: fire-and-don't-care)

https://github.com/jimimatrix/seneca-mesh-plugin-target-issue

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