-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Unstable fingerprints for trait predicates #84275
Comments
Could be a duplicate of #84269. |
@thirdsgames: The next time this happens, could you zip and upload your entire |
In retrospect that would have been an obvious thing to do (sorry) - I wanted to see if |
I've reproduced the problem (and zipped the target dir) on my linux machine. Meta
Error output:
Error output with backtrace:
|
@thirdsgames: Have you updated your version of Rust (or changed anything in |
No I haven't, I'm still running the the 2021-04-17 nightly release. But the original issue was raised with an earlier version, on a different machine, and with a clean compile, so both releases (and OSes) are affected. |
Thanks for your support! I've just read the 1.52.1 blog post, hope this ends up getting resolved! |
Context
Unfortunately I haven't been able to work out what caused this bug, and it seems to be transient, so I don't know how to make a minimal verifiable example. Source code: quill-lang. I'm sorry if this is very little information to go off!
The trait that is producing an error,
quill_common::location::Ranged
, is used in many of the sub-projects. Immediately before this error was raised, I added an import ofuse quill_common::location::Ranged;
inquill_lsp/src/main.rs
which was not there before.For context, I'm developing a Visual Studio Code extension
quill_vscode
using thesrc/quill_lsp
language server. When booting up the VSCode extension host, TypeScript (quill_vscode/client/stc/extension.ts
) runscargo run -p quill_lsp
to instantiate the language server, causingcargo
to compile my project while VSCode is already in the "debug" mode for the extension host. I don't know if this is relevant - VSCode isn't compiling any Rust projects so there doesn't seem to be a race condition between two instances ofcargo
, but I do use therust-analyzer
extension which may runcargo clippy
in the background as I edit. I do often compile using a "driver" programquill
which internally runscargo run --bin quillc ...
so it's possible that this two-layered build was the problem.The same error message is emitted each time, using the same
cargo build
command. Runningcargo clean
fixes the issue.Meta
rustc --version --verbose
:Error output
The line
overwriting quill
is produced by my debug output for an unrelated part of the project, please ignore it!Backtrace
The text was updated successfully, but these errors were encountered: