From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS29169 217.70.176.0/20 X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id CC1101F670 for ; Sat, 12 Mar 2022 21:04:13 +0000 (UTC) Received: (Authenticated sender: n@nfraprado.net) by mail.gandi.net (Postfix) with ESMTPSA id C61A11BF203 for ; Sat, 12 Mar 2022 21:04:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nfraprado.net; s=gm1; t=1647119051; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=kV17OfJEKX/asPYfHQu7OQ2gt2twF4EWe01YdecsR3Q=; b=Dwgpwu9K14rZHwUWYg3BNa3o8ZKtnjRID1eQaLzaftgnf0iv4KTBjt5HtJ+Deiq8o0Yrvv woron/kHkbcR0Ny60wfW5SPHowV2UsJh1KEJYXanTYqhis2dcfY3syB5JynfU5gpgS1/jq +j/lWOA05z6z8J884tH/l7F3ZAFkM1hYD2DIHfhNtU/Zby16XKeUNwcnsIpWQb7GwBDPPm duclQNtqx5O8G2TkpzH5kWgle2soy9tzAJIaEBiVrUaySp0obFc++NTf5n2LoKeRQ13mnT cXB/h7YFie94qqurqpDHZxvCWYp8deE+WAfQlFL1U8BgD56+CHVazBLg5m0uRA== Date: Sat, 12 Mar 2022 16:04:08 -0500 From: =?utf-8?B?TsOtY29sYXMgRi4gUi4gQS4=?= Prado To: meta@public-inbox.org Subject: Failed 'lei q' blocks 'lei init' from working Message-ID: <20220312210408.rgp232m4za4q6ln5@notapiano> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit List-Id: Hi, Right after building lei from source, I get an error running the 'q' command: [nfraprado@notapiano public-inbox]$ ./lei.sh q -I https://lore.kernel.org/all/ -o ~/.mail/lei/test --threads --dedupe=mid 'dfn:mt8192.dtsi rt:1.month.ago..' open(/home/nfraprado/.local/share/lei/store/mail_sync.sqlite3): No such file or directory at /home/nfraprado/ext/git/public-inbox/lib/PublicInbox/LeiQuery.pm line 37. That's somewhat reasonable since I haven't issued an init first. But if I then try to init: [nfraprado@notapiano public-inbox]$ ./lei.sh init # leistore.dir=/home/nfraprado/.local/share/lei/store newly initialized [nfraprado@notapiano public-inbox]$ ./lei.sh init # leistore.dir=/home/nfraprado/.local/share/lei/store newly initialized No store is ever created. If I reboot (or issue the 'e' sysrq to basically restart userspace) and then run the init command right away, it does work. So it seems to me that there's some state that is kept after running the q command which blocks init from working, hence requiring the reboot to clear that state. Not quite sure if it's a Perl thing or a bug in public-inbox, but since it's unusual behavior (and took me some time to find out) I figured I'd report it. Making 'q' run 'init' if not already done so could also help to work around this issue. Thanks, Nícolas