If I didn't overlook anything else, then issue #8 occurs after the following things happen:
HarmonyObserve (n) in harmony.js registers for events on the node.server.harmony object
Eventually a timeout occurs in harmony-server.js, which causes the exception handler to call createClient(node), which replaces node.server.harmony with a new harmony object.
The old harmony object, which carries the HarmonyObserver event registration, stops working.
No listener is ever registered on the new node.server.harmony object, hence the observer node never notices an activity change.
The merge request introduces an EventEmitter in the server that persists even when node.server.harmony objects change. Observer nodes register for events with that EventEmitter.
Feel free to edit whatever you like or to pursue an entirely different solution. I'm not too familiar with node js.
If I didn't overlook anything else, then issue #8 occurs after the following things happen:
HarmonyObserve (n)in harmony.js registers for events on thenode.server.harmonyobjectcreateClient(node), which replacesnode.server.harmonywith a newharmonyobject.harmonyobject, which carries theHarmonyObserverevent registration, stops working.node.server.harmonyobject, hence the observer node never notices an activity change.The merge request introduces an
EventEmitterin the server that persists even whennode.server.harmonyobjects change. Observer nodes register for events with thatEventEmitter.Feel free to edit whatever you like or to pursue an entirely different solution. I'm not too familiar with node js.