user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [ANNOUNCE] public-inbox 2.1.0
Date: Thu, 25 Dec 2025 09:48:31 +0000	[thread overview]
Message-ID: <20251225094822-public-inbox-2.1.0-rele@sed> (raw)

This is mainly a bugfix and Perl 5 bug workaround release on top
of 2.0.0.

The biggest fix is a workaround for Perl v5.40.x users (doesn't
affect v5.42.0+) to fix a leak and control flow bug in git blob
reconstruction from patch emails in our web UI.  Had our control
flow not been tied to Perl's refcounting, this leak would've gone
undetected for much longer.  This only affects users with coderepos
configured and associated with inboxes.
<https://yhbt.net/mirrors/perl.git/90595091f22dad07b381fd02ff1fb7e158fd8915/s/>

The new in 2.0.0+ `--split-shards' feature now works on the
SWIG Xapian bindings.  <https://trac.xapian.org/ticket/841>

public-inbox-xcpdb preserves `has_threadid' and `skip_docdata'
Xapian metadata across reshards.  This has been a long-standing
bug but only noticed by Konstantin recently.  See
https://public-inbox.org/meta/d937b906500374083a6af84c6c6442f50225ab90/s/
for a quick workaround for indices damaged by this bug.

`waitpid' calls which set $! to EINTR (which Perl auto-retries on) no
longer cause close failures when lei reads gzipped mboxes.  This was
noticed on a *BSD system without IO::KQueue, but it may affect others.

epoll_pwait errors now croak to catch EINVAL bugs caused by
alternative build systems (e.g. perl-cross) which misreport
$Config{sig_count}.

The FD_CLOEXEC flag is now set for per-port `out=' and `err='
files.  As usual, stdout and stderr remain open across execve(2).

There are also some minor C/C++ code cleanups in the xap_helper and
libgit2 helpers.

Upgrading:

  lei users must "lei daemon-kill" after installation to load
  new code.  Normal daemons (read-only, and public-inbox-watch)
  will also need restarts, of course, but there are no
  backwards-incompatible data format changes so rolling back to
  older versions is harmless.

Compatibility:

  No incompatible changes.

New users + hackers:

  The install/ directory includes tools to automate installation and
  removal of dependencies for stripped-down or full setups.  See
  install/README for more details.

  devel/try-lei now exists for testing out an empty lei instance
  without writing to an existing one.

Thanks again to Konstantin Ryabitsev and Leah Neukirchen for
their invaluable bug reports.

Please report bugs via plain-text mail to: meta@public-inbox.org

See archives at https://public-inbox.org/meta/ for all history.
See https://public-inbox.org/TODO for what the future holds.

                 reply	other threads:[~2025-12-25  9:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251225094822-public-inbox-2.1.0-rele@sed \
    --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).