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
This was caused by #14058. One resolve happens before the Initializing scheduler.../Scheduler initialized. log pair, and another after.
There are two issues here:
Why are two resolves happening in the first place? (maybe this is expected?)
Why the second one isn't using the cached result of the first one.
Regarding 2), my debugging shows that this is because the working set is different in each case. In the first resolve it contains just the lockfile, and in the second one it contains the union of the lockfile and (the transitive closure of) the plugins.
The text was updated successfully, but these errors were encountered:
As described in #14246, #14058 caused plugin loading to run twice when we missed the cache. This was because after loading plugins, the working set has changed, and represents a new set of constraints on plugin loading.
While the current behavior is accurate, it isn't useful. Instead, we adjust `PluginResolver` to make the inputs to plugin loading idempotent, even if the outputs cannot be.
Fixes#14246.
[ci skip-rust]
This was caused by #14058. One resolve happens before the
Initializing scheduler.../Scheduler initialized.
log pair, and another after.There are two issues here:
Regarding 2), my debugging shows that this is because the working set is different in each case. In the first resolve it contains just the lockfile, and in the second one it contains the union of the lockfile and (the transitive closure of) the plugins.
The text was updated successfully, but these errors were encountered: