From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] uri_imap: fix ->uidvalidity and ->uid w/ `/' separator
Date: Wed, 15 Sep 2021 08:33:47 -0400 [thread overview]
Message-ID: <20210915123347.knr4qpaei73tjc5q@meerkat.local> (raw)
In-Reply-To: <20210914221036.GA4907@dcvr>
On Tue, Sep 14, 2021 at 10:10:36PM +0000, Eric Wong wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > 2021-09-14T20:59:12Z 20428 20428 die: BUG: imaps://imap.migadu.com/lore/b4;UIDVALIDITY=1621977334 has no UIDVALIDITY at /usr/local/share/perl/5.32.1/PublicInbox/LeiStore.pm line 313.
> > (from nowait set_sync_info)
>
> Same bug, different place :x
> --------8<------
> Subject: [PATCH] uri_imap: fix ->uidvalidity and ->uid w/ `/' separator
>
> Again, we were failing to account for '/' use in mailbox names :x
The error is gone, but the saved search still doesn't show up when I run
"lei ls-search". Looking in .local/share/lei/saved-searches, I see that they
still get created as lore/foldername-${checksum}, which is probably why
ls-search doesn't find them?
-K
next prev parent reply other threads:[~2021-09-15 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 17:50 Wrong folder when using imaps:// Konstantin Ryabitsev
2021-09-14 19:35 ` [PATCH] uri_imap: handle '/' as an IMAP hierarchy separator Eric Wong
2021-09-14 19:55 ` Konstantin Ryabitsev
2021-09-14 20:12 ` Eric Wong
2021-09-14 20:19 ` Konstantin Ryabitsev
2021-09-14 21:05 ` Konstantin Ryabitsev
2021-09-14 22:10 ` [PATCH] uri_imap: fix ->uidvalidity and ->uid w/ `/' separator Eric Wong
2021-09-15 12:33 ` Konstantin Ryabitsev [this message]
2021-09-15 17:43 ` Eric Wong
2021-09-15 17:57 ` Konstantin Ryabitsev
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=20210915123347.knr4qpaei73tjc5q@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=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.
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).