Debugging doesn't work in 1.19.0-dev.7.3 SDK

[DanTup]

Using 1.19 RC SDK.

Code:

main() {
  print("test");
}

Press F5 to run under debugger; program never runs. Logged output is:

==> {"id":"0","method":"streamListen","params":{"streamId":"Isolate"}}
==> {"id":"1","method":"streamListen","params":{"streamId":"Debug"}}
<== {"jsonrpc":"2.0","id":"0","result":{"type":"Success"}}
<== {"jsonrpc":"2.0","id":"1","result":{"type":"Success"}}

Whereas in 1.18.1 we see:

==> {"id":"0","method":"streamListen","params":{"streamId":"Isolate"}}
==> {"id":"1","method":"streamListen","params":{"streamId":"Debug"}}
<== {"jsonrpc":"2.0","id":"0","result":{"type":"Success"}}
<== {"jsonrpc":"2.0","id":"1","result":{"type":"Success"}}
<== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Isolate","event":{"type":"Event","kind":"IsolateRunnable","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/243414459","name":"test.dart$main","number":"243414459"},"timestamp":1472205353653}}}
==> {"id":"2","method":"setExceptionPauseMode","params":{"isolateId":"isolates/243414459","mode":"Unhandled"}}
<== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"PauseStart","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/243414459","name":"test.dart$main","number":"243414459"},"timestamp":1472205353655}}}
==> {"id":"3","method":"resume","params":{"isolateId":"isolates/243414459"}}
<== {"jsonrpc":"2.0","method":"streamNotify","params":{"streamId":"Debug","event":{"type":"Event","kind":"_DebuggerSettingsUpdate","isolate":{"type":"@Isolate","fixedId":true,"id":"isolates\/243414459","name":"test.dart$main","number":"243414459"},"timestamp":1472205353657,"_debuggerSettings":{"_exceptions":"unhandled"}}}}

The 1.19 version never gets the IsolateRunnable event that came through in 1.18?

[devoncarew]

I don't know that the protocol has changed much recently. It's odd that the vm versions behave differently -

[rmacnak-google]

I don't see a IsolateRunnable in 1.18.1 either. I think this is a usage error, with the intended usage being

1. Subscribe to the isolate stream to learn about new isolates.
2. Call getVM learn about the isolates that were already running.

@turnidge

[DanTup]

Maybe this is a timing issue then? Maybe in 1.18.1 our subscription is being set up sooner? It's 100% reproducible for me though, those logs I posted are what I see for each version every time.

[DanTup]

Confirmed fixed by #132 :)