You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Code 513 "you don't have permission error" when clicking the dependency reset button after using local version of dependency
To Reproduce
Steps to reproduce the behavior:
open dependencies under asset/tests
on the bottom left dependencies panel, right click on swift-markdown and click use local version
pick asset/tests/Swift-Markdown folder
click the reset button in the dependencies view (the button of the left of the resolve refresh circle button)
or run the dependency test on windows
Expected behavior
Action completed successfully
Environment
OS: windows 11 x86-64
Swift version (output of swift --version): 6.0.2
Visual Studio Code version: 1.95.2
vscode-swift version: 371bbf
Additional context
According to spm dev:
Windows is well known for file locking. That's usually what that means. Could be Windows Defender inspecting the build output. Or if you have sourcekit-lsp running, it opens the index database which locks it.
I can attest to this by trying the similar commands on command line without vscode open and the error will not show up.
So we need to decide what's the appropriate behavior we want to adopt on windows.
The text was updated successfully, but these errors were encountered:
award999
changed the title
Code 513 "you don't have permission error" when clicking the dependency reset button after using local version of dependency
[windows] Code 513 "you don't have permission error" when clicking the dependency reset button after using local version of dependency
Nov 20, 2024
Describe the bug
Code 513 "you don't have permission error" when clicking the dependency reset button after using local version of dependency
To Reproduce
Steps to reproduce the behavior:
or run the dependency test on windows
Expected behavior
Action completed successfully
Environment
swift --version
): 6.0.2Additional context
According to spm dev:
Windows is well known for file locking. That's usually what that means. Could be Windows Defender inspecting the build output. Or if you have sourcekit-lsp running, it opens the index database which locks it.
I can attest to this by trying the similar commands on command line without vscode open and the error will not show up.
So we need to decide what's the appropriate behavior we want to adopt on windows.
The text was updated successfully, but these errors were encountered: