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

Error/Warning messages on network share are not navigable #74105

Open
vsfeedback opened this issue Jun 21, 2024 · 1 comment
Open

Error/Warning messages on network share are not navigable #74105

vsfeedback opened this issue Jun 21, 2024 · 1 comment
Assignees
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[regression] [worked-in:17.9.7]
Clicking on any error/warning does not react, does not jump to the code row where the problem is.
I just rolled the version back.


Original Comments

Alison Jin [MSFT] on 5/22/2024, 01:56 AM:

(private comment, text removed)

anhig on 5/22/2024, 02:30 AM:

(private comment, text removed)

anhig on 5/23/2024, 10:12 AM:

(private comment, text removed)

Feedback Bot on 5/26/2024, 06:53 PM:

(private comment, text removed)

Wenwen Fan [MSFT] on 5/28/2024, 00:20 AM:

(private comment, text removed)

anhig on 5/29/2024, 01:48 AM:

(private comment, text removed)

Wenwen Fan [MSFT] on 5/30/2024, 02:42 AM:

(private comment, text removed)

Feedback Bot on 6/12/2024, 01:44 AM:

(private comment, text removed)

anhig on 6/12/2024, 02:17 AM:

(private comment, text removed)

Wenwen Fan [MSFT] on 6/18/2024, 02:32 AM:

(private comment, text removed)

Feedback Bot on 6/20/2024, 06:07 AM:

(private comment, text removed)

frank.stutzkowski on 6/21/2024, 00:22 AM:

(private comment, text removed)


Original Solutions

(no solutions)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Jun 21, 2024
@CyrusNajmabadi
Copy link
Member

My guess is that we get a URI wrong. @dibarbet can you ptal. It may be on our end, or it may end up gonig to @kayle if we're doing things properly on hte roslyn side.

If it is our end, i'm likely to insist that we remove whatever manual file-path munging code we have :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

No branches or pull requests

3 participants