| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The inspector can accept a connection before an --inspect-brk target enters its frontend wait. Runtime.runIfWaitingForDebugger can then be handled too early, allowing the target to subsequently block forever. Wait for NodeRuntime.waitingForDebugger before initializing and releasing launched targets. Race the handshake against disconnects and apply it to both interactive and probe startup. Refs: nodejs#64116 Assisted-by: codex:gpt-5.6-sol Co-authored-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Filip Skokan <panva.ip@gmail.com>
|
The startup-readiness handshake and its initial integration were adapted from @Archkon's work in #64304. This version narrows and hardens that approach by covering disconnects during the full handshake, preserving probe-mode structured errors, and adding focused failure and cleanup tests. |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 87.79343% with 26 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #65194 +/- ##
==========================================
- Coverage 90.32% 90.12% -0.21%
==========================================
Files 760 752 -8
Lines 248525 251780 +3255
Branches 46894 47354 +460
==========================================
+ Hits 224488 226911 +2423
- Misses 15469 16210 +741
- Partials 8568 8659 +91
... and 151 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
Sorry, something went wrong.
|
I ran parallel/test-debugger-exceptions 1,000 times with -j16 on macOS 15:
The A/B result suggests this likely fixes the flake, and the code looks good to me. My only non-blocking nit is the lack of a probe-mode disconnect test while waitForDebugger() is pending. LGTM. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Thanks for adding the probe disconnect test!
This suggests that the startup handshake may deflake debugger tests beyond parallel/test-debugger-profile and parallel/test-debugger-exceptions called out in the description. Additional validation: stress test for parallel/test-debugger-profile 1,000 times with -j16 on macOS 15:
|
Sorry, something went wrong.
Assisted-by: codex:gpt-5.6-sol Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Sorry, something went wrong.
The inspector can accept a connection before an --inspect-brk target enters its frontend wait. Runtime.runIfWaitingForDebugger can then be handled too early, allowing the target to subsequently block forever. Wait for NodeRuntime.waitingForDebugger before initializing and releasing launched targets. Race the handshake against disconnects and apply it to both interactive and probe startup. Refs: #64116 Assisted-by: codex:gpt-5.6-sol Co-authored-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Filip Skokan <panva.ip@gmail.com> PR-URL: #65194 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The inspector can accept a connection before an --inspect-brk target enters its frontend wait. Runtime.runIfWaitingForDebugger can then be handled too early, allowing the target to subsequently block forever. Wait for NodeRuntime.waitingForDebugger before initializing and releasing launched targets. Race the handshake against disconnects and apply it to both interactive and probe startup. Refs: #64116 Assisted-by: codex:gpt-5.6-sol Co-authored-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Filip Skokan <panva.ip@gmail.com> PR-URL: #65194 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The inspector can accept a connection before an --inspect-brk target enters its frontend wait. Runtime.runIfWaitingForDebugger can then be handled too early, allowing the target to subsequently block forever. Wait for NodeRuntime.waitingForDebugger before initializing and releasing launched targets. Race the handshake against disconnects and apply it to both interactive and probe startup. Refs: #64116 Assisted-by: codex:gpt-5.6-sol Co-authored-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Archkon <180910180+Archkon@users.noreply.github.com> Signed-off-by: Filip Skokan <panva.ip@gmail.com> PR-URL: #65194 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Important
This ought to deflake parallel/test-debugger-profile and parallel/test-debugger-exceptions.
The inspector can accept a connection before an --inspect-brk target enters its frontend wait. Runtime.runIfWaitingForDebugger can then be handled too early, allowing the target to subsequently block forever.
Wait for NodeRuntime.waitingForDebugger before initializing and releasing launched targets. Race the handshake against disconnects and apply it to both interactive and probe startup.
Refs: #64116
Assisted-by: codex:gpt-5.6-sol