public inbox for goredo-devel@lists.stargrave.org
Atom feed
From: goredo <spacefrogg-goredo@spacefrogg•net>
To: goredo-devel@lists.cypherpunks.ru
Subject: Re: resource deadlock avoided messages
Date: Sun, 24 Sep 2023 13:17:40 +0200 (GMT+02:00) [thread overview]
Message-ID: <4cd15382-990f-4229-9aa9-2aade0ad4ab3@spacefrogg.net> (raw)
In-Reply-To: <ZQ85olPBGYJGOyv7@stargrave.org>
Is it really an issue when goredo is unable to grab a lock? Maybe print the warning after 10 seconds if the situation persist. So, the user gets a response why redo is stuck on some target. The warning was confusing, because, to me, it hinted at some error in my set of redo targets, as if I was constructing dependency loops or so. It looks strange to me to get informed about some issues, which I have no means to fix. Let's see, how 1.31 performs for that project...
–Michael
next prev parent reply other threads:[~2023-09-24 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 19:12 Several issues since 1.30 spacefrogg
2023-09-23 19:16 ` resource deadlock avoided messages Sergey Matveev
2023-09-24 11:17 ` goredo [this message]
2023-09-25 16:14 ` Sergey Matveev
2023-09-23 19:16 ` Target runs multiple times in single session Sergey Matveev
2023-09-23 19:17 ` Slow/buffered output of targets finished messages Sergey Matveev
2023-09-23 19:17 ` Unclear what target the output relates to Sergey Matveev
2023-09-24 11:10 ` goredo
2023-09-25 16:20 ` Sergey Matveev
2023-09-28 13:55 ` spacefrogg
2023-09-30 16:57 ` Sergey Matveev
2023-10-16 13:24 ` Sergey Matveev