-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clearly spell out the lifetime of IDs used in the protocol #60
Comments
If we see a sequence of messages from VSCode that does not follow these guidelines - e.g. an attempt to do an "evaluate" immediately after sending "next" (which invalidated all frame IDs, and so the one that comes in "evaluate" is no longer valid), is that a client bug? If so, where should it be filed? |
yes, I that's a client bug. @isidorn but it's tricky for the client to figure this out, correct? |
Yeah it is a bit tricky, since we do some ui optimisations (e.g we refresh the watch element with a slight timeout and thus it can happend that you get a stale evaluate). |
/duplicate #35 |
The general rule for ID lifetime in DAP is:
This should be more clearly spelled out in the protocol.
The text was updated successfully, but these errors were encountered: