From: ori@eigenstate.org
To: 9front@9front.org
Subject: [9front] gefs -- this fix is important
Date: Wed, 22 May 2024 21:54:29 -0400 [thread overview]
Message-ID: <866AF43BF4D069FD91C53627562B3F4D@eigenstate.org> (raw)
Bug in ORCLOSE, where we were missing a lock around upserting.
Asserts would *probably* catch it, but it can cause some pretty
bad issues if not.
Sysupdate and get the fix -- and thanks to the testers using
it and reporting the crashes!
reply other threads:[~2024-05-23 1:57 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=866AF43BF4D069FD91C53627562B3F4D@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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 NNTP newsgroup(s).