Danny Tuppeny

I'm cleaning up the issue tracker and closing things that aren't likely to be addressed in the foreseeable future. I don't have a good solution here, and I feel like...

@christopherfujino what's your plan for https://github.com/flutter/flutter/pull/121373? I think in order to avoid breaking anything, we need to: 1. change the default in Flutter, but keep the flag (so `--show-web-server-device` does...

@eliasyishak if the plan is to re-land https://github.com/flutter/flutter/pull/121373, then it needs to be done in a non-breaking way. Then we can update Dart-Code here to stop using it when it's...

Closing this because it's not currently actionable until it's clear what the plan/goal is for the Flutter change. We need to land non-breaking changes in Flutter first before we can...

There is another error printed before it which has English error text, but the call stack is no different (it also has a different line, so I don't know if...

btw, when just testing something else, I noticed these bad errors show up in the user-facing messages too - slightly different between wasm/js, but both bad messages. WASM:  JS:...

Releases were published a short while ago :-) https://github.com/dart-lang/test/pull/2495 https://pub.dev/packages/test I haven't started on the `pkg:test_reflective_loader` changes yet, but I don't expect them to take long so may get to...

I've opened a PR for this at https://github.com/dart-lang/tools/pull/2090

@scheglov thanks! My main motivation here is to roll this into the SDK which I think just pulls this whole repo from a git hash, so there's no urgency to...

Cannot reproduce... seems like this check always prevents it: https://github.com/Dart-Code/Dart-Code/blob/622472f313ac69e98102e6d243ce9969c3ad64e3/src/extension/sdk/update_check.ts#L16