public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: "Kernel.org Tools" <tools@kernel.org>,
	Andi Shyti <andi.shyti@kernel.org>
Subject: Re: korgalore bug: Feed state not found for lch@ list
Date: Wed, 11 Feb 2026 16:20:21 +0100	[thread overview]
Message-ID: <bc8445cc-f57f-48c0-b45a-747ac916d5b2@kernel.org> (raw)
In-Reply-To: <20260211-gigantic-aspiring-jaguarundi-aeddcd@lemur>

On 11/02/2026 16:14, Konstantin Ryabitsev wrote:
> On Tue, Feb 10, 2026 at 05:30:31PM +0100, Krzysztof Kozlowski wrote:
>> "/home/krzk/.local/share/pipx/venvs/korgalore/lib/python3.13/site-packages/korgalore/lore_feed.py",
>> line 77, in clone_epoch
>>     raise RemoteError(f"Git clone failed: {output.decode()}")
>> korgalore.RemoteError: Git clone failed:
> 
> Ah, so in this particular case I wasn't testing with the actual --shallow
> parameter, which is why I couldn't reproduce the failure. The problem here
> is that the lch list doesn't have any messages since November 2025, so when we
> try to clone it with --shallow-since=1.week.ago, we get a clone failure.
> 
> There is a workaround for this situation in both master and stable-0.5.y, and
> I can confirm that setting up the lch list works without a crash now.
> 
> If you can confirm, I will tag 0.5.2 for the release.

I tried master branch and works, thanks!

Best regards,
Krzysztof

      reply	other threads:[~2026-02-11 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 20:52 korgalore bug: Feed state not found for lch@ list Krzysztof Kozlowski
2026-02-09 20:17 ` Konstantin Ryabitsev
2026-02-10 16:30   ` Krzysztof Kozlowski
2026-02-11 15:14     ` Konstantin Ryabitsev
2026-02-11 15:20       ` Krzysztof Kozlowski [this message]

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=bc8445cc-f57f-48c0-b45a-747ac916d5b2@kernel.org \
    --to=krzk@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=mricon@kernel.org \
    --cc=tools@kernel.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