Skip to content

service/dap: set seq number for response messages#4280

Merged
derekparker merged 1 commit into
go-delve:masterfrom
aarzilli:dapseq
Mar 10, 2026
Merged

service/dap: set seq number for response messages#4280
derekparker merged 1 commit into
go-delve:masterfrom
aarzilli:dapseq

Conversation

@aarzilli
Copy link
Copy Markdown
Member

@aarzilli aarzilli commented Mar 9, 2026

The DAP specification says that messages sent from the server to the
client should have a seq number but we never did do that because the
original DAP extension didn't.

Add sequence numbers, even though it doesn't seem to cause problems in
practice, to conform to the protocol specification.

Fixes #2245

@aarzilli aarzilli force-pushed the dapseq branch 2 times, most recently from 8a77df4 to 8d46fd6 Compare March 9, 2026 09:13
Comment thread service/dap/server.go
The DAP specification says that messages sent from the server to the
client should have a seq number but we never did do that because the
original DAP extension didn't.
Add sequence numbers, even though it doesn't seem to cause problems in
practice, to conform to the protocol specification.

Fixes go-delve#2245
Copy link
Copy Markdown
Member

@derekparker derekparker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekparker derekparker merged commit a0db158 into go-delve:master Mar 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

service/dap: set seq field in responses

2 participants