-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ICE: forcing query with already existing DepNode
#10298
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
Comments
It seems to be the lambda specified here: https://github.com/serai-dex/serai/blob/97951e3f4fcef1be3ad1693228883fe9a2e3709b/processor/src/signer.rs#L154-L159 Fully specifying it prevents this ICE from occurring. I attempted to write a MRE premised on a similar pattern, yet was unable to get it to trigger. |
I'm not able to reproduce this. Here's what I tried:
|
It may no longer be an issue. I have not had this pop up over the past month (though that may just be since I patched the lambda to no longer trigger this). The only note I'd make is I generally run Thanks for spending the time. If it's not reproducible, I won't complain about closing this. |
I also ran into this
I considered zipping my project including target folder, but it's almost 15 GB (Cargo caching has dementia) so I decided against. |
Closing as this is a rustc incremental issue. |
Summary
https://github.com/serai-dex/serai/tree/97951e3f4fcef1be3ad1693228883fe9a2e3709b/processor is the crate which triggered this (and exact commit). While I do not have a MRE, I hope this either serves as an additional stack trace, or that the ~350 line file the backtrace specifies is sufficiently small/readable.
Even without a fix being made available, I'd greatly appreciate if the underlying problem was identified so I can workaround this.
Version
Error output
Backtrace
The text was updated successfully, but these errors were encountered: