-
-
Notifications
You must be signed in to change notification settings - Fork 182
Avoid deadlock with multiple connections when executing code and new connection opens #294
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
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
fe5855b
fix(phpDebug,xdebugConnection): Avoid deadlock with multiple connecti…
jonyo 17c8ea0
fix(xdebugConnection): isExecuteCommand does not need to be optional
jonyo 064abdc
docs(xdebugConnection): Adding jsdoc for Connection._pendingExecuteCo…
jonyo 48ca0f4
fix(xdebugConnection): set _pendingExecuteCommand before resolving th…
jonyo e8cadff
refactor(phpDebug): Do not wait when setting breakpoints if the conne…
jonyo 5bbc91b
style(phpDebug): Applying pretty code changes
jonyo 35612ca
Merge branch 'master' into deadlock
jonyo 97c5db9
fix(phpDebug): The first index could be skipped, so always set vscode…
jonyo dcbeebc
refactor(phpDebug): No need to chain all promises, just the first one…
jonyo d145cb9
docs(phpDebug): Adding back inline comments and renaming a var
jonyo 7d80911
refactor: improve error handling and simplify
felixfbecker 31948fa
refactor: use async/await again
felixfbecker File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I simplified the code and noticed that you removed these
ifchecks. Was that intentional?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@felixfbecker Yes, because connectionIndex of 0 could be the connection that is waiting for PHP code to execute, connectionIndex 1 would be the "new" connection that is able to execute right away so is able to set the value in time for it to matter.
Plus all it is doing is setting a value and the value is fixed, it doesn't save time by skipping it if already set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I understand. There is a slight behaviour change here in that now if any of the connections errored, the breakpoint will be marked us unverified, whereas before, only the first connection determined the fate of the breakpoint. This is fine I guess.