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

Exception UI link detection fails for paths with brackets #28508

Closed
michelkaporin opened this issue Jun 12, 2017 · 6 comments
Closed

Exception UI link detection fails for paths with brackets #28508

michelkaporin opened this issue Jun 12, 2017 · 6 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@michelkaporin
Copy link
Contributor

For example
c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:30196

detects as link only the last part: Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:30196.

@michelkaporin michelkaporin added the bug Issue identified by VS Code Team member as probable bug label Jun 12, 2017
@michelkaporin michelkaporin added this to the Backlog milestone Jun 12, 2017
@michelkaporin michelkaporin self-assigned this Jun 12, 2017
@michelkaporin michelkaporin changed the title Exception UI link detection fails for paths with spaces Exception UI link detection fails for paths with brackets Jun 14, 2017
@rajkumar42
Copy link
Contributor

@michelkaporin I have a fix in the works, but it only accounts for rooted paths. Can you provide some samples of callstacks in node, I can make sure the regex work with those.

@michelkaporin
Copy link
Contributor Author

Typical node callstack looks like that on Windows:

    at Object.activateColorDecorations (c:\GIT\vscode\extensions\css\client\out\colorDecorators.js:42:44)
    at c:\GIT\vscode\extensions\css\client\out\cssMain.js:50:40
    at process._tickCallback (internal/process/next_tick.js:103:7)

Accounting for rooted paths is also good. Is it part of your c# regex PR? Or you plan to address it next?

@rajkumar42
Copy link
Contributor

For C# we only account for rooted paths. Looks like from your example, node can have unrooted paths. I suppose the file path can be with and without parenthesis?

at process._tickCallback (internal/process/next_tick.js:103:7)
at internal/process/next_tick.js:103:7

my current PR does not account for unrooted paths in node.

@rajkumar42
Copy link
Contributor

@michelkaporin seems like node has lot of cases, i've backed out my change for the node's regex. We would just like to get the C# file path parser in this time.

@michelkaporin
Copy link
Contributor Author

@rajkumar42 lets keep the discussion in your PR, rather than this issue. You can solve this issue for c# extension, not necessary to address node also.

@isidorn
Copy link
Contributor

isidorn commented Oct 27, 2017

Closing as dup of #34026

@isidorn isidorn closed this as completed Oct 27, 2017
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 27, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants