Simon Tournier writes:
> IMHO, the next actions are:
>
> a) Replace this message:
>
> (message (format #f "You found a bug: the program '~a'
> failed to compute the derivation for Guix (version: ~s; system: ~s;
> host version: ~s; pull-version: ~s).
> Please report the COMP
Hi,
As Ian pointed out earlier, here some “guix pull” bugs:
55066
58309 closed
61520 closed
62023 closed
62830
And most of them are transient or hard to reproduce. More had been
listed in [1], it reads:
63451
63830
64489
64659 v1.4.0
64753
64963
Politely, my relatively-new-user observations about `guix pull` and home/system
reconfigure commands,
1. The commands, in my experience, always fail with network troubles, and the
commands must be re-issued multiple times for
things to complete. Other internet-requesting utilities such as wget,
> Just a quick side note that some members in our community (not I) are
> offended by the word "bug" to describe software defects.
welcome to the internet of billions of people, where the cost of expressing
one's offence doesn't cost anything anymore, and there are dozens of offended
people eve
Simon Tournier writes:
> More than often, the issue is transient, hard if not impossible to
> reproduce and thus hard to analyze. Even, when it happens for me,
> sometimes I say ok let try to collect some information for helping in
> debugging that but then just running again “guix pull” makes i
Hi,
On Sun, 21 Jul 2024 at 15:16, Ludovic Courtès wrote:
>>> I’m fine removing the “report a bug” message, maybe replacing it with
>>> some clearer diagnostic and suggestion? WDYT?
>>
>> Could we detect if it comes from networking? Somehow catch the error
>> and run some code that checks stuff
Hi,
Simon Tournier skribis:
> On Mon, 17 Jun 2024 at 14:59, Ludovic Courtès wrote:
>
>>> It doesn’t feel great to tell users to report a bug for things that
>>> aren’t bugs. They’re either closed, or never followed up on; it’s a
>>> poor experience on both ends.
>>
>> I agree, it’s pretty bad.
Hi,
On Mon, 17 Jun 2024 at 14:59, Ludovic Courtès wrote:
>> It doesn’t feel great to tell users to report a bug for things that
>> aren’t bugs. They’re either closed, or never followed up on; it’s a
>> poor experience on both ends.
>
> I agree, it’s pretty bad.
>
> I’m fine removing the “report
Felix Lechner via "Development of GNU Guix and the GNU System distribution."
writes:
> On Mon, Jun 17 2024, Ludovic Courtès wrote:
>
>> I’m fine removing the “report a bug” message [...] WDYT?
>
> Just a quick side note that some members in our community (not I) are
> offended by the word "bug"
Hi Ludo' & Ian,
On Mon, Jun 17 2024, Ludovic Courtès wrote:
> I’m fine removing the “report a bug” message [...] WDYT?
Just a quick side note that some members in our community (not I) are
offended by the word "bug" to describe software defects. Perhaps here
is a chance to replace it?
Kind reg
Hi,
Ian Eure skribis:
> Is there some way for this code to be smarter about when it prints the
> "report a bug" message, so it doesn’t tell users to report bugs when
> none exist? Is there a way for it to notice that the problem is
> related to networking, and tell the users to try again in a l
There’s a steady number of bug reports generated by the "You found
a bug" message which happens during `guix pull's. The
overwhelming majority of these reports are caused by networking
problems or the Guix infrastructure being unreliable or
overloaded. Many of these were submitted during the
12 matches
Mail list logo
