Skip to content
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

[Bug]: Debugger is getting hanged while debugging through playwright extension #30883

Closed
sat1591 opened this issue May 17, 2024 · 7 comments
Closed

Comments

@sat1591
Copy link

sat1591 commented May 17, 2024

Version

1.1.2

Steps to reproduce

  1. Create a sample tests in playwright TS
  2. Put a debugger on any line
  3. go to playwright extension
  4. select any test
  5. click on debug to running the tests in debug mode

Expected behavior

Expected the tests should start initiating the browser and hit the break point which I can debug.

Actual behavior

After clicking the debug button the tests are not running anything. The debugger is just hanged like I showed in screenshot.
When downgraded my extension version to 1.0.22 the debugging is running as expected. This problem I have noticed in 1.1.1 and 1.1.2

image

Additional context

No response

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (4) x64 AMD EPYC 7763 64-Core Processor
    Memory: 4.90 GB / 15.95 GB
  Binaries:
    Node: 20.12.2 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    VSCode: 1.88.1 - C:\Program Files\Microsoft VS Code\bin\code.CMD
  npmPackages:
    @playwright/test: ^1.43.1 => 1.43.1
@mxschmitt

This comment was marked as outdated.

@mxschmitt
Copy link
Member

Please retry in v1.1.4 which we just released.

@HarneyTester
Copy link

HarneyTester commented May 20, 2024

Hi, we didnt raise the original ticket but we have the same issue in v1.1.4

@pavelfeldman
Copy link
Member

We can't reproduce this issue. We need exact steps to be able to reproduce: exact project repo or a zip file, exact steps to follow.

@HarneyTester
Copy link

HarneyTester commented May 21, 2024

I'll see what I can put together. I actually think its the same as #30743, although this is closed.

@mxschmitt
Copy link
Member

mxschmitt commented May 21, 2024

@sat1591 @HarneyTester, could you try v1.1.5? This issue should be addressed in the latest extension update.

@HarneyTester
Copy link

Yes all working for me now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants