Subject: Re: resource deadlock avoided messages

From: goredo <[email-masked]>
Date: Sun, 24 Sep 2023 13:17:40 +0200 (GMT+02:00)

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