public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: dirk@juniper.net
To: gnats-gnats@sourceware.cygnus.com
Subject: gnats/218: PRs fail to show up in index
Date: Fri, 13 Jul 2001 15:34:00 -0000	[thread overview]
Message-ID: <20010713223036.28639.qmail@sourceware.cygnus.com> (raw)

>Number:         218
>Category:       gnats
>Synopsis:       PRs fail to show up in index
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 13 15:34:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     dirk bergstrom, juniper networks, inc.
>Release:        gnats 4.0a
>Organization:
>Environment:
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.
>How-To-Repeat:
run a busy gnats installation.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-13 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13 15:34 dirk [this message]
2001-08-16  1:14 Yngve Svendsen

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=20010713223036.28639.qmail@sourceware.cygnus.com \
    --to=dirk@juniper.net \
    --cc=gnats-gnats@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: 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).