Auto-reconnect support #1
Merged
Conversation
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
savannahostrowski
force-pushed
the
auto-reconnect
branch
from
79e9ec7 to
ea38bfe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds logic to handle
--reloadby automatically re-injecting debugpy into newly spawned worker processes.Note on workflow: When running in
--reloadmode, editing a file causes VSCode to detach (because uvicorn kills the old worker and spawns a new one with a different PID). The debugwand session stays alive and auto-reinjects debugpy into the new worker, but you need to manually press F5 in VSCode to reconnect. This is a limitation of the Debug Adapter Protocol - there's no way to tell VSCode to automatically reconnect when the process it was attached to dies.