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
As a user it's not obvious to me how spago manages it's internal registry index. If I need a newly published version of a library, even when explicitly declaring it's version, spago will refuse to install it until it also decides it should refresh it's index. This is a frustrating experience, and it would be nice to have some control over this process.
The text was updated successfully, but these errors were encountered:
Agreed, we should expose this with a flag. OnlineBypassCache was recently added (together with the registry transfer command), so we didn't get around to exposing this yet.
I'm interested in adding this as I'm hitting the issue very frequently, but just adding a parser for this flag isn't enough, I don't think. I ran an install --ensure-ranges --bypass-cache, and it just seems to be pulling the registry over and over again in a loop 😄. I'm assuming it's doing this for every package as it attempts to make some sort of build plan.
As a user it's not obvious to me how spago manages it's internal registry index. If I need a newly published version of a library, even when explicitly declaring it's version, spago will refuse to install it until it also decides it should refresh it's index. This is a frustrating experience, and it would be nice to have some control over this process.
The text was updated successfully, but these errors were encountered: