From: Christina O'Donnell <cdo@mutix.org>
To: 68359@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>,
ShinyZero0 <shinyzero0@tilde.club>
Subject: bug#68359: Can't pull my channel because of, getaddrinfo -8 error
Date: Sun, 14 Apr 2024 11:47:50 +0100 [thread overview]
Message-ID: <deecb047-0dbf-a1f7-ac53-f6fb7443bddc@mutix.org> (raw)
In-Reply-To: <CYAMI74CD75T.3JZWP3FK5PE6Q@fedora>
Hi Simon, Paul,
I've also run into this bug and I believe it is due to the error being
cached. This is clearly undesirable so this issue should stay open until
that is resolved.
My reasoning for thinking it is a cache issues is:
- An issue with package transformations should never cause an
getaddrinfo error as Guix generally only goes up to servers for channels
and build packages.
- I ran into this after my gitlab instance had some outage, and
persisted since my server came back up.
- Pulling from a duplicate ref with the same hash succeeds, indicating
that the bug occurs before the checkout is fetched.
I'm happy to have a stab at working on this. Currently working on
reproducing this, it's not as simple as making the channel url point at
a closed port (eg. https://localhost:1212). I even tried binding a SCTP
server to the port, but I just get connection refused. Anyone have any
ideas about this?
Should the title be changed to something like "Guix can cache
getaddrinfo failures on `guix pull`"? (.. on the assumption that I'm
proven right ;-)
I'll assign this to myself, if there are no objections.
Kind regards,
Christina
prev parent reply other threads:[~2024-04-14 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 1:09 bug#68359: Can't pull my channel because of getaddrinfo -8 error ShinyZero0
2024-01-13 11:50 ` Josselin Poiret via Bug reports for GNU Guix
2024-01-13 23:42 ` ShinyZero0
2024-01-14 13:33 ` ShinyZero0
[not found] ` <handler.68359.B.170484900520013.ack@debbugs.gnu.org>
2024-01-18 2:50 ` bug#68359: Acknowledgement (Can't pull my channel because of getaddrinfo -8 error) ShinyZero0 via Bug reports for GNU Guix
2024-03-08 18:10 ` Simon Tournier
2024-04-14 10:47 ` Christina O'Donnell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=deecb047-0dbf-a1f7-ac53-f6fb7443bddc@mutix.org \
--to=cdo@mutix.org \
--cc=68359@debbugs.gnu.org \
--cc=shinyzero0@tilde.club \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).