From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: [PATCH 0/7] lei: more half-baked updates Date: Fri, 29 Jan 2021 12:42:53 +0500 [thread overview] Message-ID: <email@example.com> (raw) I'm not sure if I want to keep 1/7. 4/7 is LONG overdue Still chasing down difficult-to-reproduce lei2mail workers segfaults which seem related to LeiDedupe + SharedKV and weird object lifetimes; which is preventing me from doing anything else. Worst case is we disable worker processes, but the performance hit sucks. Eric Wong (7): ipc: wq: support passing fields to workers lei_xsearch: drop repeated "Xapian" in error message ipc: more consistent behavior between worker types lei: less error-prone FD mapping git: synchronous cat_file may return type and OID ipc: move on_destroy scope to inside the eval shared_kv: simplify PID+object guard for cleanup lib/PublicInbox/Git.pm | 9 ++--- lib/PublicInbox/IPC.pm | 46 +++++++++++++--------- lib/PublicInbox/LEI.pm | 56 ++++++++++++++++++++------- lib/PublicInbox/LeiOverview.pm | 9 ++--- lib/PublicInbox/LeiToMail.pm | 8 +--- lib/PublicInbox/LeiXSearch.pm | 70 +++++++++++++++------------------- lib/PublicInbox/SharedKV.pm | 8 ++-- lib/PublicInbox/Spawn.pm | 2 +- t/git.t | 8 ++-- t/shared_kv.t | 2 +- 10 files changed, 119 insertions(+), 99 deletions(-)
next reply other threads:[~2021-01-29 7:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-29 7:42 Eric Wong [this message] 2021-01-29 7:42 ` [PATCH 1/7] ipc: wq: support passing fields to workers Eric Wong 2021-01-29 7:42 ` [PATCH 2/7] lei_xsearch: drop repeated "Xapian" in error message Eric Wong 2021-01-29 7:42 ` [PATCH 3/7] ipc: more consistent behavior between worker types Eric Wong 2021-01-29 7:42 ` [PATCH 4/7] lei: less error-prone FD mapping Eric Wong 2021-01-29 7:42 ` [PATCH 5/7] git: synchronous cat_file may return type and OID Eric Wong 2021-01-29 7:42 ` [PATCH 6/7] ipc: move on_destroy scope to inside the eval Eric Wong 2021-01-29 7:43 ` [PATCH 7/7] shared_kv: simplify PID+object guard for cleanup 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/7] lei: more half-baked updates' \ /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
Code repositories for project(s) associated with this 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).