From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] upas/fs lstk(), one more time
Date: Sun, 01 Oct 2023 00:20:17 -0400 [thread overview]
Message-ID: <A25A032B-F8EB-437D-AD5E-AA64CDD3972C@stanleylieber.com> (raw)
In-Reply-To: <4F3D2C9093B9D1B31C1623A8A7A7B41A@eigenstate.org>
On October 1, 2023 12:13:41 AM EDT, ori@eigenstate.org wrote:
>Quoth sl@stanleylieber.com:
>> i backed up my mbox and added messages back in batches, checking after
>> each batch that upas/fs was still able to open it. i did this until i
>> found a specific message upas/fs choked on.
>>
>> sl
>
>is it possible to reproduce it with just that message? would
>you be comfortable sending it over to someone for debugging?
>
>
unfortunately, the precise message causing the problem turned out to contain sensitive information. i am pretty sure this is the first time upas/fs has refused to index a message for me, but if it happens again, if possible, i'll share the offending malformed message so we can name and shame the villain.
sl
next prev parent reply other threads:[~2023-10-01 4:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 21:38 sl
2023-10-01 0:35 ` sl
2023-10-01 1:51 ` Benjamin Purcell
2023-10-01 4:13 ` ori
2023-10-01 4:20 ` Stanley Lieber [this message]
2023-10-01 9:32 ` hiro
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=A25A032B-F8EB-437D-AD5E-AA64CDD3972C@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).