PlutoPkg: if Pkg.resolve fails, try updating the registries #2298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When opening a notebook (e.g. from the web), we call
Pkg.resolve
on the notebook environment. If this fails, we try some strategies one-by-one to automatically fix the problem until it resolves. These strategies are:[compat]
entries from the Project.toml (added in Recover gracefully from loading a notebook with non-existing versions #2294)This should improve the situation of #2280. Before this PR, Pluto would try strategy 2, fail, then strategy 3 which works. But this removes all compat entries for all packages, including packages that had no problems, and installs latest versions for all.
After this PR, strategy 1 would already work, and the notebook would run with the intended package versions.