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
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
The description is somewhat of a guess, and I'm not sure how to reproduce it reliably.
I checked out the gl_generators crate and opened it in VSCode, causing RLS to start compiling it. I then ran cargo build in a console in the same directory. The build failed because link.exe was unable to open target\debug\deps\serde_derive-aa8d0da7f64aa69e.dll.
Despite the RLS having finished (showed as doing nothing in VSCode) when I tried to manually delete the file in explorer it said it could not delete the file because it was in use by the RLS. This was the reason why the build was unable to complete.
The text was updated successfully, but these errors were encountered:
@Diggsey this was hopefully fixed in today's (or yesterday's?) nightlies. Could you please try updating with rustup to newest nightly/RLS and see if the problem persists?
The description is somewhat of a guess, and I'm not sure how to reproduce it reliably.
I checked out the
gl_generators
crate and opened it in VSCode, causing RLS to start compiling it. I then rancargo build
in a console in the same directory. The build failed becauselink.exe
was unable to opentarget\debug\deps\serde_derive-aa8d0da7f64aa69e.dll
.Despite the RLS having finished (showed as doing nothing in VSCode) when I tried to manually delete the file in explorer it said it could not delete the file because it was in use by the RLS. This was the reason why the build was unable to complete.
The text was updated successfully, but these errors were encountered: