Danny Tuppeny
Danny Tuppeny
Maybe related to https://github.com/dart-lang/sdk/issues/48501 Seems there was an attempted fix to allow calling `flush()` to trigger the exception so it can be caught, but that was reverted in https://github.com/dart-lang/sdk/commit/97d8445e5f6395293f458761fe628588dd8ecb6a I'm...
Ah, I see. I'll see if I can easily make it work that way. It's not super convenient to have to handle all the exceptions in one handler away from...
@aam I tried implementing handling the error there (and some other tweaks to handle cases where things shut down), but sometimes I see the test just hang. I attached DevTools...
> I'm not sure whether this "Allocation Location" points to a place where it's waiting or the place where the receive port was created. Sorry, I think you're right. Although...
(if it makes sense to open a new issue about this, let me know - it's probably not entirely related to the issue here, but it may prevent fixing it...
> How are you running this? Are you running this as part of debug_attach_test.dart? Just in a standalone Dart script with `dart foo.dart` (on Windows). Happens at least with a...
My understanding of that is that the `Future` returned by `runZonedGuarded` isn't guaranteed to complete. In this case it is, because the rest of the program is running. However, if...
Here's the complete stack (using the [original repro above](https://github.com/dart-lang/sdk/issues/55313#issuecomment-2122319013)): ``` #0 new _RawReceivePort._ (dart:isolate-patch/isolate_patch.dart:138:55) #1 new _RawReceivePort (dart:isolate-patch/isolate_patch.dart:132:34) #2 new RawReceivePort (dart:isolate-patch/isolate_patch.dart:65:34) #3 _NativeSocket.connectToEventHandler (dart:io-patch/socket_patch.dart:1599:23) #4 _NativeSocket.sendToEventHandler (dart:io-patch/socket_patch.dart:1592:5) #5 _NativeSocket.setListening...
Thanks - I've opened a CL to remove the zone. Although, we got a bit sidetracked - I don't think that was the original issue here, which is an exception...
> Nothing obvious stands out to me. I'm guessing this is related to the issues related to writing to a closed stdin sink? I'm not sure... catching the error being...