Slava Egorov

I just did some measurements for @dnfield, so I am going to include them here. If we take `test/rendering` folder of Flutter package and run all tests from a clean...

If you think that no changes will be necessary in `package:test` or `package:test_core` to fix it on Flutter side then I guess we should just close this one. I can't...

Should work according to https://github.com/dart-lang/test/issues/1509, but indeed does not work. Must be a regression. /cc @bkonyi @natebosch

I think this is fixed by https://github.com/dart-lang/stack_trace/commit/d3e4c4d633eca379462dd4473b8995761155ee84 and https://github.com/dart-lang/sdk/commit/a52f2b96179ebdf29c38cab47e73dd1c6ec6bdff

Hmm, indeed stack trace produced by `Chain.capture` is still broken. I guess something in the `stack_trace` internals is still not working properly. But `StackTrace.current` is actually producing normal stuff now...

I can take a look next week

Do you have some specific issue for me to look at? e.g. do you have an example code I could run which prints meaningless stack-trace? I am just unsure what...

@escamoteur The documentation for `Chain.capture` says: > Note that if callback produces multiple unhandled errors, `onError` may be called more than once. That's what you are seeing here. TBH, I...

It can spawn multiple asynchronous operations in parallel and not listen to either, e.g. ```dart void foo() { Future.delayed(const Duration(milliseconds: 10), () => throw 'One'); Future.delayed(const Duration(milliseconds: 10), () =>...

Note that `let` is a non-final binding in JavaScript so it can be confusing for people coming from JS.