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

Exclude fragments from urlFilter matching #869

Closed
yrtimiD opened this issue Nov 27, 2020 · 4 comments
Closed

Exclude fragments from urlFilter matching #869

yrtimiD opened this issue Nov 27, 2020 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality

Comments

@yrtimiD
Copy link

yrtimiD commented Nov 27, 2020

Attach to chrome with remote debug fails without any error message since code 1.51.1. In 1.50 all worked fine.
Chrome version is latest 57.0.4280.66, started with --remote-debugging-port=9222 and inspector is available from other chrome on http://localhost:9222/

To Reproduce

  1. use linked launch.json
  2. start chrome with --remote-debugging-port=9222
  3. Code -> Run -> select "Attach to Chrome" -> click play button

in 1.50 debugger toolbar appears and "Call stack" is populated with available pages,
in 1.51.1 debugger toolbar appears without "disconnect" button, and nothing in "Call Stack"

Log File
launch.json and debugadapter.json

VS Code Version: 1.51.1

Additional context
"Launch in chrome" still works perfectly.

@yrtimiD yrtimiD added the bug Issue identified by VS Code Team member as probable bug label Nov 27, 2020
@connor4312
Copy link
Member

connor4312 commented Nov 28, 2020

Can you try with the nightly build? I think the changes in #834 should fix this. In 1.50 (or maybe 1.49, I forget) we briefly introduced a change that made this work, but rolled it back with https://github.com/microsoft/vscode-chrome-debug/issues/719#issuecomment-705072583; the fix in 834 is the correct solution.

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Nov 28, 2020
@connor4312
Copy link
Member

connor4312 commented Nov 28, 2020

Actually, I think it will still not work. Basically you want the url to actually be exactly http://localhost/#, or alternatively specify a urlFilter like http://localhost/*. We can probably ignore url fragments when matching debug urls.

@connor4312 connor4312 added feature-request Request for new features or functionality and removed bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster labels Nov 28, 2020
@yrtimiD
Copy link
Author

yrtimiD commented Nov 28, 2020

@connor4312 , specifying "url" exactly as in browser made it work. In my case it was "url": "http://localhost/#".
Adding "urlFilter": "http://localhost/*" instead of url also fixes the issue.

@connor4312 connor4312 changed the title Chrome attach is broken since 1.51.1 Exclude fragments from urlFilter matching Dec 18, 2020
@connor4312
Copy link
Member

Actually I realized I already fixed this in #840. It's been released as of VS Code 1.52.

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants