public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com> To: nobody@sourceware.cygnus.com Cc: gnats-prs@sourceware.cygnus.com Subject: Re: gnats/218: PRs fail to show up in index Date: Thu, 16 Aug 2001 01:14:00 -0000 [thread overview] Message-ID: <20010816081401.8354.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR gnats/218; it has been noted by GNATS. From: Yngve Svendsen <yngve.svendsen@clustra.com> To: dirk@juniper.net, gnats-gnats@sourceware.cygnus.com Cc: Subject: Re: gnats/218: PRs fail to show up in index Date: Thu, 16 Aug 2001 10:07:43 +0200 At 22:30 13.07.2001 +0000, dirk@juniper.net wrote: >FreeBSD aphid.juniper.net 4.2-STABLE FreeBSD 4.2-STABLE >a gnats database with ~16000 PRs, and ~100 frequent users. >~60 PRs modified per day, ~30 PRs added per day. > >Description: >several times a week, PRs disappear from the index (or, in the >case of new PRs, never show up). this renders them effectively >invisible, and causes great consternation among users. > >regenerating the index fixes the problem, but that locks up the >the database for a couple minutes, which annoys users. > >interestingly, gnats comes with a database monitoring script, >check-db.sh, which looks for inconsistencies in the index, so >this would appear to be a known problem. Dirk, I have seen similar things on GNATS 3.x, where submitting PRs by mail with long Subject fields corrupts the index in such a way that some PRs are effectively rendered invisible. Could this be the problem here? Could you have a look at the PRs that disappear and maybe send me one of them? - Yngve
next reply other threads:[~2001-08-16 1:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-16 1:14 Yngve Svendsen [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-13 15:34 dirk
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=20010816081401.8354.qmail@sourceware.cygnus.com \ --to=yngve.svendsen@clustra.com \ --cc=gnats-prs@sourceware.cygnus.com \ --cc=nobody@sourceware.cygnus.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: linkBe 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).