Hi Simon, Simon Tournier <zimon.touto...@gmail.com> writes:
> Hi, > > The bug tracker – or guix-devel and/or help-guix – reports several > similar issues: “guix pull” fails and then run it again (or again and > again and …) makes it pass. Well, part of the collection: > > https://issues.guix.gnu.org/issue/62830 > https://issues.guix.gnu.org/issue/63451 > https://issues.guix.gnu.org/issue/63830 > https://issues.guix.gnu.org/issue/64489 > https://issues.guix.gnu.org/issue/64659 > https://issues.guix.gnu.org/issue/64753 > https://issues.guix.gnu.org/issue/64963 > > It is hard to know if all have the same root and/or they are the trace > of the same bug but there is an issue with “guix pull”. For example > #64302 and #64489 had been merged but based on #64489 message, I am not > convinced the issue is the same as the reported by #64302. Anyway. > > Recently, I had to run several times “guix pull” in a row. And on > another machine, I did it with --no-substitutes because I was tired. > > Well, I do not know how to tackle this: most of the time the issue is > not reproducible because it depends on substitute servers. > > Any idea about what could be unexpected or what needs some love? I haven't checked the above links, but I think something that would help in this regard is better handling of network issues. E.g, don't print a backtrace on the first connection failure; retry maybe 3 times then print a helpful error mentioning the network appears unreliable. -- Thanks, Maxim
