You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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
andactor-without-plugin.js
) run the same 'seneca.act' code, but one does so as a plugin and the other does not. Whenobserver.js
throws an error,actor-with-plugin.js
crashes, butactor-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
The text was updated successfully, but these errors were encountered: