From: "sergiodj at sergiodj dot net" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27531] New: Support retry of failed downloads
Date: Sat, 06 Mar 2021 07:46:06 +0000 [thread overview]
Message-ID: <bug-27531-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27531
Bug ID: 27531
Summary: Support retry of failed downloads
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: sergiodj at sergiodj dot net
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
While running Debian's debuginfod service, I have received a bunch of
complaints from people who are living far from where the server is located
(Europe) and are getting a few timeouts when GDB attempts to download the
debuginfo files.
It would be nice if we could configure debuginfod-client to retry N times
before giving up. I thought about opening this bug against GDB, but I think it
makes more sense to implement this in the debuginfod client itself so that
everyone can benefit from it.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-06 7:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 7:46 sergiodj at sergiodj dot net [this message]
2021-03-06 18:08 ` [Bug debuginfod/27531] " fche at redhat dot com
2021-03-07 2:34 ` fche at redhat dot com
2021-03-07 20:38 ` sergiodj at sergiodj dot net
2021-03-07 22:04 ` fche at redhat dot com
2021-03-14 17:14 ` zsj950618 at gmail dot com
2021-03-14 17:16 ` zsj950618 at gmail dot com
2021-03-14 17:29 ` fche at redhat dot com
2021-03-14 18:02 ` zsj950618 at gmail dot com
2021-03-14 18:03 ` zsj950618 at gmail dot com
2021-03-14 22:58 ` fche at redhat dot com
2021-03-14 23:07 ` sergiodj at sergiodj dot net
2021-03-18 16:54 ` fche at redhat dot com
2021-07-09 13:58 ` mark at klomp dot org
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27531-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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.
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).