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
Good question... I was in revert mode only but my theory is that it sends a message before we are ready for it to be processed (it sends something in a ctor-call).
After some investigation: this is not about the ctor.
TPromise and Promise behave in the same way around the invocation order of the ctor.
The difference is the invocation of then, where Promise always invokes then on the next tick. The result of the promise is an IMessagePassingProtocol and in between those ticks to invoke the then handler, a message (or more) get lost.
I will look into how it would be possible to refactor this... It would almost need pause/resume functionality on IMessagePassingProtocol...
This commit 7224bb3 apparently broken debug in weird ways. The
$registerDebugTypes
was called anymore. This commit fixed it again:407a485
The text was updated successfully, but these errors were encountered: