Kristoffer Carlsson
Kristoffer Carlsson
I tried this. On: - Revise (this PR) - LoweredCodeUtils master - JuliaInterpreter master - Julia 1.12.0-beta1 What I did was: - Load Revise, Tensors. - Make the following revision...
Bug reports about resolver issues pretty much need to also provide `Project.toml`, `Manifest.toml` and the exact Julia version to be actionable. Or at least steps to reproduce those.
Right now, `resolve` tries to keep the current versions fixed. https://github.com/JuliaLang/Pkg.jl/blob/b2bc8627c2835e2b78cf7213e034f17130d534ce/src/API.jl#L331 You could use `update` instead.
@aravindh-krishnamoorthy, what in that randomness would cause the allocations to go "from a couple GB of memory to hundreds of gigabytes" in your opinion?
I don't really like this because `Registry.update` is automatically called in various places and you don't want the pkg operation to completely fail if one of the registries fail to...
Maybe only do this if it is not the default. I feel it would be a bit verbose/confusing to showing it every time.
Should be fixed by https://github.com/JuliaLang/Pkg.jl/issues/2830.
> I ran tests on github actions for several versions, and both 1.11s fail with a different error: That is known: https://github.com/JuliaLang/julia/issues/52986. The error for this comes from PkgEval on...
Seems like a bug in MiKTeX. Maybe it is possible to do a bug report upstream?
https://tex.stackexchange.com/questions/710109/error-message-about-windows-10-even-though-im-on-windows-10 don't think there is anything we can do here.