From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH 3/3] v2writable: done: force synchronous awaitpid
Date: Wed, 20 Nov 2024 19:06:58 +0000 [thread overview]
Message-ID: <20241120190658.M920857@dcvr> (raw)
In-Reply-To: <20241119214752.1883670-4-e@80x24.org>
Pushed as commit 99fc3d76968aacaea55f5b98b5b5a4d2314bc97c
with the following commit message:
v2writable: done: force synchronous awaitpid
We need to shut down shards synchronously to reliably release
the inbox write lock when inside the DS event loop (as the
lei/store subprocess is, unlike most v2writable users).
This seems to fix long-running `lei import' failures to
lei/store after repeated tests. It is a good idea anyways to
ensure exit status of shard workers are correct before returning
from ->done.
prev parent reply other threads:[~2024-11-20 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 21:47 [PATCH 0/3] write-related fixes Eric Wong
2024-11-19 21:47 ` [PATCH 1/3] v2writable: use DS and import now() sub Eric Wong
2024-11-19 21:47 ` [PATCH 2/3] treewide: warn on SQLite `PRAGMA optimize' failure Eric Wong
2024-11-19 21:47 ` [PATCH 3/3] v2writable: done: force synchronous awaitpid Eric Wong
2024-11-20 19:06 ` Eric Wong [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://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=20241120190658.M920857@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.
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).