Platform
macOS
Reproduction
This bug does not affect debugging in Nova, but it does have a minor affect on debugging in VS Code.
I am inspecting the messages between the client and the Playdate Simulator debugger using sudo tcpdump -i lo0 -A tcp port 55934
.
- Open a Playdate project
- Build the project
- Debug the game using the Playdate Simulator debugger
- Press the stop button in the client
Expected
- The client sends:
{ "command":"initialize", "type":"request" }
- The server responds with:
{ "command":"initialize", "type":"response", "success":true,", "supportsTerminateRequest":true }
- The client sends:
{ "type": "request", "command": "terminate" }
- The server responds with:
{ "type": "response", "command": "terminate", "success": true }
Actual
- The client sends:
{ "command":"initialize", "type":"request" }
- The server responds with:
{ "command":"initialize", "type":"response", "success":true,", "supportsTerminateRequest":true }
- The client sends:
{ "type": "request", "command": "terminate" }
- The server responds with:
{"command":"terminate","message":"Unsupported method: terminate","type":"response","success":false}
I see that Nova sends a disconnect
command instead of a terminate
command. VS Code attempts to send a terminate
command first and then a disconnect
command second if the terminate
fails as mentioned in this issue.