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
It appears that in some cases an AngularActor which quickly emits/broadcasts an event possibly while angular is still loading, that event is never handed by the listeners.
The text was updated successfully, but these errors were encountered:
It seems in some cases comet will eventually retry the messages, and they are all received in order as expected. Perhaps we could use our random ID to create a queue on the client for holding these messages until angular returns a scope for our actor. In the meantime, I'm going to regard this as not terribly important.
It appears that in some cases an
AngularActor
which quickly emits/broadcasts an event possibly while angular is still loading, that event is never handed by the listeners.The text was updated successfully, but these errors were encountered: