From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id E06061F47A for ; Fri, 30 Aug 2024 19:45:09 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=baylibre-com.20230601.gappssmtp.com header.i=@baylibre-com.20230601.gappssmtp.com header.a=rsa-sha256 header.s=20230601 header.b=oiSsq+sa; dkim-atps=neutral Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-714263cb074so1714125b3a.1 for ; Fri, 30 Aug 2024 12:45:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20230601.gappssmtp.com; s=20230601; t=1725047107; x=1725651907; darn=public-inbox.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=UJF93UgcuYhpABdY3GLgT9RR0TLp0gBdb/4/6ZiIxyE=; b=oiSsq+sa9VVPyv3GJrY3GTVWKKT882gU82oIyqXyNUsFjZa2AYKkGc9Zdlm41X4ZZU XgPxKyRxVARDsJ5dl3tI6ZlLd0c/duICNfpl/oHXq/LJ3c1HO5oEi7DMeQS3woyCg+/T 7ilej6KfLSfPTOGdi5TfX0DgPkKqx0Zk+hSabYS9okf1vMr8qoeuXN177vDKTGMSoSn8 0yWp7Zj+WtZyiLw1IimrcaxcGbOQ/pDvtfrZYouTWmsDzDloBwlPo0/STX/DjDUF7lhD D14Avxy9va056MsFg6B2jBS9RYaMGaCsHJZ5/JGSSFfIwIPz+D0B4nFCpYctLBSrE0qc FgCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725047107; x=1725651907; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=UJF93UgcuYhpABdY3GLgT9RR0TLp0gBdb/4/6ZiIxyE=; b=J4BZPWFXk8cAxAZARz+7JaJ6vTGMH1wIxlZo6tBZhRzO9pFK0Jz951xDMIAelvoMr2 Rng2Tb9+CpVKiZQU/1QM0bREPutO/fcBtXXqIsYigEEUuVzRmnknC9HCVTzom3r/ggEV imn32y5DUNAwSSJcta5+rXP6YRZEVdaS0SX862sx8nzCSWAw/7XtBxqWURxkjAzKsP+x Utb9ZIFmoyo20NrkrmyFonaJrNjU0TU4C5awET1mF+GmlcFQfrT+LotoQabIbBv+A/Q/ PYnx2mxt9tcVD7ppp00VTM5j6akQ3vsUW2aY1S8QDe/mRuPpcpCbwxjW5+EhHeirEkg+ eCcA== X-Gm-Message-State: AOJu0YwGRdRlBi8PbV02KhqHGQsiR/0eFdF9zGQZeWBGa5Ium/Cp+CvQ L9nTR9W8yE77pIpg3+qSXqAMHLo4ClFtobNdKrJFeMQGbW8Gcq5gqLzDaonFvOCxkMZMwgq3oEo Wl4TxatB8EpXkQ4u5JbomRDRLOn9PV+8ruPRJKcHvEwR1v/or X-Google-Smtp-Source: AGHT+IFFSkSbWcFVIEk1XQCrKB/j5kZ7lb9W6SKG7/NhgZ9VfjYj0nmOqXZtx+AwKRtzvm+WauE0s9X+2hjHJpIaTuE= X-Received: by 2002:a05:6a20:c90d:b0:1c4:bbb8:5050 with SMTP id adf61e73a8af0-1cce10a998emr7473023637.37.1725047107313; Fri, 30 Aug 2024 12:45:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Hilman Date: Fri, 30 Aug 2024 12:44:56 -0700 Message-ID: Subject: Re: Exception: Expected block 59423 to be level 2, not 0 To: meta@public-inbox.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: On Fri, Aug 30, 2024 at 12:40=E2=80=AFPM Kevin Hilman wrote: > > I recently started seeing this error for `lei up`: > > $ lei up -v dummy > Exception: Expected block 59423 to be level 2, not 0 > > The same thing happens when trying an edit-search: > > $ lei edit-search dummy > Exception: Expected block 59423 to be level 2, not 0 > > The same thing happens whether "dummy" is a valid saved-search or not. > A bit of searching suggests that this is a xapian error. I have > xapian-tools installed on this server, should I run some checks on the > xapian db? If so, where is it stored? Everything I find under > ~/.local/share/lei seems to be sqlite3 db. I forgot to mention, I'm running the v1.9.0 tag of public-inbox, but also tried with the master branch and got the same results. Kevin