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

[6.0] Normalize Windows drive letter to be uppercase #1881

Closed

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Dec 11, 2024

  • Explanation: VS Code spells file paths with a lowercase drive letter, while the rest of Windows APIs use an uppercase drive letter. Because of this casing inconsistency, we don’t show diagnostics on Windows. Normalize the drive letter spelling to be uppercase to fix the issue.
  • Scope: LSP messages on Windows that use a lowercase drive letter
  • Risk: Only affects Windows but modifies that at a very central position. But uppercasing the drive letter for internal processing should be safe.
  • Testing: Verified that we show diagnostics with this fix
  • Issue: SourceKit-LSP not publishing diagnostics on Windows #1855 / rdar://141001203
  • Reviewer: @bnbarham on Normalize Windows drive letter to be uppercase #1880

@ahoppen ahoppen requested a review from bnbarham December 11, 2024 00:15
@ahoppen
Copy link
Member Author

ahoppen commented Dec 11, 2024

@swift-ci Please test

VS Code spells file paths with a lowercase drive letter, while the rest of Windows APIs use an uppercase drive letter. Normalize the drive letter spelling to be uppercase.

Fixes swiftlang#1855
rdar://141001203
@ahoppen ahoppen force-pushed the 6.0/normalize-drive-letter branch from 53df6b2 to 9fa5200 Compare December 11, 2024 18:31
@ahoppen
Copy link
Member Author

ahoppen commented Dec 11, 2024

@swift-ci Please test

@ahoppen
Copy link
Member Author

ahoppen commented Jan 13, 2025

@swift-ci Please build toolchain Windows

@ahoppen
Copy link
Member Author

ahoppen commented Jan 13, 2025

@swift-ci Please build toolchain

@ahoppen ahoppen closed this Feb 27, 2025
@vault-thirteen
Copy link

Closed with unmerged commits

Why unmerged ? Has this problem been fixed ?

@ahoppen
Copy link
Member Author

ahoppen commented Feb 28, 2025

This issue has been fixed in Swift 6.1 toolchains for quite a while now and I think it’s unlikely that we’ll release an updated 6.0 toolchain for this fix.

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

Successfully merging this pull request may close these issues.

None yet

2 participants