@b-laporte actually I've tried this yesterday, it was not working, somebody else should have fixed someting...

Could it be a side effect of 9b08ab3 ?

Humm... I still have errors in Dart for

@vicb yes indeed something has changed as this PR didn't work yesterday - and I actually prepared another PR to include Future.sync() (through a new PromiseWrapper.sync()) as it was solving the issue - but when I rebased to submit the PR I discovered that everything was working without the new changes (!) - so I simply dropped my original PR for this new one... But the real discovery for me was to learn that try/catch in dart in an async call stack doesn't work at all as in JavaScript (good to know - but a bit scary to have a common code base..) - cf. https://www.dartlang.org/articles/futures-and-error-handling/

In Dart you can have string !== string if one of them is interned, there should be no pb with .toEqualthough.

I haven't had time to check what is wrong with the Promise/Future error handling. We should create an issue to investigate, can you do it ?

@ViB I would be fine to open an issue - but for this I need a error sample, and I can't reproduce it anymore - what happened was that the error was not caught in internal try/catch and was caught in the zone instead. But now everything works as expected..

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}