From: noam@pixelhero.dev
To: 9fans@9fans.net
Subject: [9fans] neoventi: call for initial testing
Date: Mon, 08 Dec 2025 17:30:27 -0500 [thread overview]
Message-ID: <15FCDAB3D76AF86D4FE56DF4E4BFA5E2@pixelhero.dev> (raw)
My reimplementation of venti[1], presented previously at IWP9, has
gone from "this will DEFINITELY eat your data in the first five
seconds" to "this will probably eat your data in the first five
minutes."
Any brave souls interested in testing it are invited to do so. I'll
definitely look at any stack traces or bugs or corruption you find,
but I can't promise to be able to recover data. It'll _probably_ be
recoverable. Probably.
Use at your own risk, yadda yadda, I'm only starting testing it with
fossil presently, but all the obvious tests I could think of offhand
are passing.
That means that all the remaining bugs are _subtle_, which is _more_
dangerous.
- Noam Preil
[1] https://git.sr.ht/~pixelherodev/neoventi
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d8ba4236feb5d92-Mdc787dc2648256807ea74cbe
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2025-12-08 19:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 22:30 noam [this message]
2025-12-10 18:54 ` [9fans] Re: neoventi: call for initial testing wb.kloke
2025-12-10 20:59 ` ori
2025-12-10 21:20 ` wb.kloke
2025-12-10 21:36 ` ori
2025-12-10 21:56 ` wb.kloke
2025-12-11 3:06 ` noam
2025-12-11 3:13 ` noam
2025-12-11 1:59 ` noam
2025-12-11 1:58 ` noam
2025-12-10 21:53 ` ori
2025-12-11 3:11 ` noam
2025-12-11 3:21 ` noam
2025-12-10 22:01 ` wb.kloke
2025-12-10 22:36 ` ori
2025-12-10 22:37 ` wb.kloke
2025-12-11 3:09 ` noam
2025-12-11 0:01 ` [9fans] Venti: design discussion noam
2025-12-10 20:28 ` wb.kloke
2025-12-10 20:49 ` Steve Simon
2025-12-11 1:16 ` noam
2025-12-10 21:22 ` wb.kloke
2025-12-11 1:52 ` noam
2025-12-10 22:07 ` wb.kloke
2025-12-12 12:08 ` [9fans] neoventi: call for initial testing Charles Forsyth
2025-12-12 17:57 ` wb.kloke
2025-12-13 0:42 ` noam
2025-12-13 0:39 ` noam
2026-01-09 5:50 ` noam
2026-01-09 13:24 ` wb.kloke
2026-01-09 14:31 ` wb.kloke
2026-01-09 16:07 ` Noam Preil
2026-01-09 16:06 ` Noam Preil
2026-01-09 5:54 ` noam
2026-01-09 17:10 ` wb.kloke
2026-01-10 20:23 ` Noam Preil
2026-01-09 17:14 ` Calvin via 9fans
2026-01-09 18:30 ` wb.kloke
2026-01-10 2:08 ` Calvin via 9fans
2026-01-10 10:46 ` Emery
2026-01-21 1:53 ` ori
-- strict thread matches above, loose matches on Subject: below --
2025-12-11 10:27 hahahahacker2009
2025-12-12 2:16 ` noam
2025-12-11 23:09 ` Charles Forsyth
2025-12-12 0:10 ` Jacob Moody
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=15FCDAB3D76AF86D4FE56DF4E4BFA5E2@pixelhero.dev \
--to=noam@pixelhero.dev \
--cc=9fans@9fans.net \
/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).