Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with files name cases.

See original GitHub issue

I had the same issue: https://github.com/elm-tooling/elm-language-client-vscode/issues/123

I’ve debuged it, so the reason is that vscode has some buggy behavior with files that changed name cases (were renamed) and file uri inside DiagnosticsProvider is not normalized, so it results that it can not find it in currentDiagnostics map.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

razzeeecommented, Nov 8, 2020

Which is something the issue template asks for. And a step by step reproduction.

On Sat, Nov 7, 2020, 23:16 Alex notifications@github.com wrote:

This probably only windows related issue, as Linux and windows treat file name cases differently.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/elm-tooling/elm-language-client-vscode/issues/129#issuecomment-723502025, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNLEZGJR76ZWGMS72LNHX3SOXBMPANCNFSM4TFO226A .

0reactions

wclrcommented, Nov 7, 2020

This probably only windows related issue, as Linux and windows treat file name cases differently.