From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kyle@kyleam.com>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS16276 188.165.0.0/16
X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,
	RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.2
Received: from out2.migadu.com (out2.migadu.com [188.165.223.204])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 4C3261F8C8
	for <meta@public-inbox.org>; Tue, 28 Sep 2021 23:21:21 +0000 (UTC)
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1;
	t=1632871279;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type;
	bh=CB5a02imSxs0N9wwW0otDUiPPGoPyBd/y/d9GtjkPoc=;
	b=qAjNHxQkWeV506nbsLdSM3XIcxQbUnrIuQLo9yZ8DZWMTCHx+VKzybRBgFAmldp36satLI
	hEFj6UdMzUTLhxISPSUZ90euYmpr9BMYaIKDoNEaseRIB167naiDm7GGAOQ8UpiZnrxIk5
	HFA/V7qIOJg7uzI9ImIN+D2hBO0BGp3yrJkkqJ9epUbELfaDhknQU+i4gJ4+45gTStcyt2
	8DCTgtCFPhQRgC/WVqsEOAZXcxuTohc28XbQzabj3puJZ/u8TVZlpbpDgsr2r957OFf1uZ
	FWvVW1OUHuvmm1r9nCjTH0zTLbr+oyTSnqPcnt/eNXwrqgz4Q4RpJB+0iR4e6A==
From: Kyle Meyer <kyle@kyleam.com>
To: meta@public-inbox.org
Subject: solver: 'BUG {try_gits} empty' error
Date: Tue, 28 Sep 2021 19:21:10 -0400
Message-ID: <87o88cqobd.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: kyle@kyleam.com
List-Id: <meta.public-inbox.org>

I've been noticing a good number of these error messages:

  E: BUG {try_gits} empty at /usr/local/share/perl/5.28.1/PublicInbox/SolverGit.pm line 80.

I think I started seeing it after a recent upgrade.  (The last revision
bump on my server was from c9c1aabe2 to 840c1c80c, and the one before
that was from c497e38cf.)  It doesn't look like SolverGit.pm has changed
recently, but perhaps some upstream code changed.  Or perhaps I'm
completely wrong about it being new.

It doesn't seem to be particular to my server because I was able to
trigger it on <http://public-inbox.org/meta> too.  Two examples:

* http://public-inbox.org/meta/5ada1f49e4dc/s/?b=lib/PublicInbox/Fetch.pm#n6

  debug log:
  
  solving 5ada1f49e4dc ...
  E: BUG {try_gits} empty at /usr/local/share/perl/5.28.1/PublicInbox/SolverGit.pm line 80.


* http://public-inbox.org/meta/41438cf79b15/s/?b=xt/net_writer-imap.t#n122

  debug log:
  
  solving 41438cf79b15 ...
  E: BUG {try_gits} empty at /usr/local/share/perl/5.28.1/PublicInbox/SolverGit.pm line 80.

Both of those recovered after a bit (first hard refresh?).

Any ideas?

Thanks.