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 text was updated successfully, but these errors were encountered:
sfackler
changed the title
'Forcing query with already existing DepNode' on new nightly
'Forcing query with already existing DepNode' panic on new nightly
Aug 31, 2018
It usually means that two distinct query keys map to the same DepNode. There should be a one to one mapping between query keys and their corresponding DepNode. The DepNode for complex keys like this is created by hashing the value of the key. Problems arise if something in the key is not hashed properly.
@nikomatsakis or @eddyb might know more about what could be wrong with the hashing of this particular query key (or might know who knows best).
This panic has appeared in the newest nightly while working on a large internal project:
The text was updated successfully, but these errors were encountered: