Re: guix-pull prints stack trace

[Alex Vong <alexvong1995@gmail.com>]

taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:

> Alex Vong <alexvong1995@gmail.com> writes:
>
[...]
>
> The bug I introduced to guix pull (while speeding it up) that has a tiny
> chance of causing a thread race related error has never been fixed.
> Maybe it's related to that.
>
> As of e714797 I can't reproduce the error; guix pull runs fine to
> completion.  Possibly a commit after c41d97b "fixed" the issue again by
> changing the order of autoloads or some such.  But it could also be
> related to the number of cores on my machine, how much you moved around
> your pointer device recently, or the phase of the moon. :-\
>
> If you still hit the error, or anyone else does, I'll get to work on it
> ASAP.
>
Yes, commit e714797 'gnu: pdf: Remove erroneous module import.' seems to
have fixed the issue again. Thanks for your attention. I don't know
there is a potential race condition in guix-pull. I will keep this in
mind.

> Otherwise, I'm quite out of the loop but IIRC there was some talk of an
> entirely different guix pull mechanism, that uses git pull or so?  If
> so and if this bug continues to trigger extremely rarely, then I'm not
> sure if it would be worth the effort to make bigger changes to the
> current 'guix pull' mechanism.
>
> Taylan
>
>
> P.S.: Feel free to contact me on Freenode (nick 'taylan') if you want to
> bypass email for quicker communication.

Thanks,
Alex