search

jest-community / vscode-jest

The optimal flow for Jest based testing in VS Code
MIT License
2.83k stars 291 forks source link

[BUG] Cannot debug on VSCode 1.88 #1136

Closed lamuertepeluda closed 5 months ago

lamuertepeluda commented 5 months ago

Describe the bug

Debugging tests seem not to work anymore in VSCode 1.88, macOS 14.4.1 M2 Pro Chipset

Perhaps related to https://github.com/microsoft/vscode/issues/209785

To Reproduce Steps to reproduce the behavior:

  1. Select a test file (file explorer or text explorer or test code)
  2. Add some breakpoints
  3. Click on 'debug test'
  4. The test execution runs without respecting the breakpoints

Expected behavior

Debugger stops at test breakpoints

I Prerequisite

Additional context

See VSCode issue, see also https://github.com/firsttris/vscode-jest-runner/issues/362 (similar extension, same problem)

The fastest (and the most fun) way to resolve the issue is to submit a pull request yourself. If you are interested, please check out the contribution guide, we look forward to seeing your PR...

webhype commented 5 months ago

Similar (or same) problem here, Debugger attached no longer appears in the terminal pane as expected, and the little debugger control window (allowing to pause / single step / exit) disappears shortly after initiating a "debug" session. After that the program executes without any debugging help. Had to downgrade to 1.87.2. Not fixed in 1.89 either. Same hardware config as OP.

KyleLehtinenDev commented 5 months ago

I also encountered this problem on 1.88 and had to downgrade to 1.87.2 as @webhype mentioned to get debugging back for my typescript apps.

Edit: Actually, my issue may relate to using NODE_OPTIONS=--dns-result-order=ipv4first as part of an attempt to get testcontainers working with rancher-desktop...

connectdotz commented 5 months ago

The underlying issue (microsoft/vscode#209785) is closed, and the fix has been released in vscode 1.88.1.

@lamuertepeluda, @webhype, @KyleLehtinenDev, could you guys update the vscode to verify if that resolved your issue?

lamuertepeluda commented 5 months ago

The underlying issue (microsoft/vscode#209785) is closed, and the fix has been released in vscode 1.88.1.

@lamuertepeluda, @webhype, @KyleLehtinenDev, could you guys update the vscode to verify if that resolved your issue?

I updated to 1.88.1 and I am now able to use the debugger again! Thanks

connectdotz commented 5 months ago

thanks @lamuertepeluda. closing this issue as resolved.