From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH v2] extindex: guard against buggy unrefs
Date: Thu, 14 Oct 2021 21:09:53 +0000 [thread overview]
Message-ID: <20211014210953.M934295@dcvr> (raw)
In-Reply-To: <20211014060629.GA14615@dcvr>
Eric Wong <e@80x24.org> wrote:
> I noticed some unref messages which shouldn't have been
> happening, but they were. Which is troubling. So add
> a guard around an unref path until we can get to the bottom
> of this.
And now I'm not seeing it... Heisenbugs :<
next prev parent reply other threads:[~2021-10-14 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 5:49 [PATCH] extindex: guard against buggy unrefs Eric Wong
2021-10-14 6:06 ` [PATCH v2] " Eric Wong
2021-10-14 21:09 ` Eric Wong [this message]
2021-10-16 1:48 ` [PATCH] extindex: avoid triggering a buggy unref Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211014210953.M934295@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).