GNU bug report logs - #66169
merge commits may harm your cache maybe?

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66169 in the body.
You can then email your comments to 66169 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Roman Riabenko <roman <at> riabenko.com>
To: bug-guix <at> gnu.org
Subject: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sat, 23 Sep 2023 22:02:47 +0300

[Message part 1 (text/plain, inline)]

I am trying to upgrade my guix systems. I ran guix pull and now I am
trying to run guix system reconfigure. It failed on two different
machines with the same backtrace. Please see the full backtrace
attached. The error message from it:

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Git error: object not found - no match for id
(4f35ff1275e05be31f5d41464ccf147e9dbfd016)


$ guix describe
Generation 28	Sep 23 2023 19:30:36	(current)
  guix 4f35ff1
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016

Considering that I experience it on two guix machines with different
system configurations, I assume that there is some bug somewhere.

Roman

[backtrace.txt (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 66169 <at> debbugs.gnu.org (full text, mbox):

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Roman Riabenko <roman <at> riabenko.com>, 66169 <at> debbugs.gnu.org
Subject: Re: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 10:37:28 +0200

Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
> I am trying to upgrade my guix systems. I ran guix pull and now I am
> trying to run guix system reconfigure. It failed on two different
> machines with the same backtrace. Please see the full backtrace
> attached. The error message from it:
> 
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Git error: object not found - no match for id
> (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
> 
> 
> $ guix describe
> Generation 28   Sep 23 2023 19:30:36    (current)
>   guix 4f35ff1
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: master
>     commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016
> 
> Considering that I experience it on two guix machines with different
> system configurations, I assume that there is some bug somewhere.
Experiencing the same for commit
35fd25af9bbcce84908101a9f487ba106a8d6df7.  I would hazard a guess that
it's due to them being merge commits.  Interestingly, allow-downgrades
does not have an effect on this message.

Cheers

Message #11 received at 66169 <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Cc: Roman Riabenko <roman <at> riabenko.com>, 66169 <at> debbugs.gnu.org
Subject: Re: bug#66169: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 08:49:57 +0000

[Message part 1 (text/plain, inline)]

Liliana Marie Prikler <liliana.prikler <at> gmail.com> skribis:

> Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
>> I am trying to upgrade my guix systems. I ran guix pull and now I am
>> trying to run guix system reconfigure. It failed on two different
>> machines with the same backtrace. Please see the full backtrace
>> attached. The error message from it:
>> 
>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>> Git error: object not found - no match for id
>> (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
>> 
>> 
>> $ guix describe
>> Generation 28   Sep 23 2023 19:30:36    (current)
>>   guix 4f35ff1
>>     repository URL: https://git.savannah.gnu.org/git/guix.git
>>     branch: master
>>     commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016
>> 
>> Considering that I experience it on two guix machines with different
>> system configurations, I assume that there is some bug somewhere.
> Experiencing the same for commit
> 35fd25af9bbcce84908101a9f487ba106a8d6df7.  I would hazard a guess that
> it's due to them being merge commits.  Interestingly, allow-downgrades
> does not have an effect on this message.
>
> Cheers

I reconfigured two machines using commit
4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
machines, I didn't get this "no match for id" issue.
That's strange...

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 66169 <at> debbugs.gnu.org (full text, mbox):

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: Roman Riabenko <roman <at> riabenko.com>, 66169 <at> debbugs.gnu.org
Subject: Re: bug#66169: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 10:56:25 +0200

Am Sonntag, dem 24.09.2023 um 08:49 +0000 schrieb Guillaume Le
Vaillant:
> Liliana Marie Prikler <liliana.prikler <at> gmail.com> skribis:
> 
> > Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
> > > I am trying to upgrade my guix systems. I ran guix pull and now I
> > > am
> > > trying to run guix system reconfigure. It failed on two different
> > > machines with the same backtrace. Please see the full backtrace
> > > attached. The error message from it:
> > > 
> > > ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> > > Git error: object not found - no match for id
> > > (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
> > > 
> > > 
> > > $ guix describe
> > > Generation 28   Sep 23 2023 19:30:36    (current)
> > >   guix 4f35ff1
> > >     repository URL: https://git.savannah.gnu.org/git/guix.git
> > >     branch: master
> > >     commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016
> > > 
> > > Considering that I experience it on two guix machines with
> > > different
> > > system configurations, I assume that there is some bug somewhere.
> > Experiencing the same for commit
> > 35fd25af9bbcce84908101a9f487ba106a8d6df7.  I would hazard a guess
> > that it's due to them being merge commits.  Interestingly,
> > allow-downgrades does not have an effect on this message.
> > 
> > Cheers
> 
> I reconfigured two machines using commit
> 4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
> machines, I didn't get this "no match for id" issue.
> That's strange...
Do you have provenance tracking on your machines (the default)?

Message #17 received at 66169 <at> debbugs.gnu.org (full text, mbox):

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Roman Riabenko <roman <at> riabenko.com>, 66169 <at> debbugs.gnu.org
Cc: Guillaume Le Vaillant <glv <at> posteo.net>
Subject: Re: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 11:16:57 +0200

Am Sonntag, dem 24.09.2023 um 10:37 +0200 schrieb Liliana Marie
Prikler:
> Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
> > ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> > Git error: object not found - no match for id
> > (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
> Experiencing the same for commit
> 35fd25af9bbcce84908101a9f487ba106a8d6df7.

Am Sonntag, dem 24.09.2023 um 08:49 +0000 schrieb Guillaume Le
Vaillant:
> I reconfigured two machines using commit
> 4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
> machines[.]

I now have a workaround that looks quite odd.  If you 
  $ sudo rm -rf /root/.cache/guix
guix system will rerun the indexing and thus pick up the new commits. 
I will dub this "advanced cache invalidation" since it appears as
though we are looking up commits in the wrong cache.

Cheers

Message #20 received at 66169 <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Cc: Roman Riabenko <roman <at> riabenko.com>, 66169 <at> debbugs.gnu.org
Subject: Re: bug#66169: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 09:22:49 +0000

[Message part 1 (text/plain, inline)]

Liliana Marie Prikler <liliana.prikler <at> gmail.com> skribis:

> Am Sonntag, dem 24.09.2023 um 08:49 +0000 schrieb Guillaume Le
> Vaillant:
>> Liliana Marie Prikler <liliana.prikler <at> gmail.com> skribis:
>> 
>> > Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
>> > > I am trying to upgrade my guix systems. I ran guix pull and now I
>> > > am
>> > > trying to run guix system reconfigure. It failed on two different
>> > > machines with the same backtrace. Please see the full backtrace
>> > > attached. The error message from it:
>> > > 
>> > > ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>> > > Git error: object not found - no match for id
>> > > (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
>> > > 
>> > > 
>> > > $ guix describe
>> > > Generation 28   Sep 23 2023 19:30:36    (current)
>> > >   guix 4f35ff1
>> > >     repository URL: https://git.savannah.gnu.org/git/guix.git
>> > >     branch: master
>> > >     commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016
>> > > 
>> > > Considering that I experience it on two guix machines with
>> > > different
>> > > system configurations, I assume that there is some bug somewhere.
>> > Experiencing the same for commit
>> > 35fd25af9bbcce84908101a9f487ba106a8d6df7.  I would hazard a guess
>> > that it's due to them being merge commits.  Interestingly,
>> > allow-downgrades does not have an effect on this message.
>> > 
>> > Cheers
>> 
>> I reconfigured two machines using commit
>> 4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
>> machines, I didn't get this "no match for id" issue.
>> That's strange...
> Do you have provenance tracking on your machines (the default)?

Yes. I use an additional channel, not only the "guix" default channel.
Maybe that makes a difference...

[signature.asc (application/pgp-signature, inline)]

Message #29 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Paul Szenher <88paul98 <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Re: bug#66169: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Mon, 25 Sep 2023 04:30:34 -0400

On 9/24/23 5:22 AM, Guillaume Le Vaillant wrote:
> Liliana Marie Prikler <liliana.prikler <at> gmail.com> skribis:
> 
>> Am Sonntag, dem 24.09.2023 um 08:49 +0000 schrieb Guillaume Le
>> Vaillant:
>>> Liliana Marie Prikler <liliana.prikler <at> gmail.com> skribis:
>>>
>>>> Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
>>>>> I am trying to upgrade my guix systems. I ran guix pull and now I
>>>>> am
>>>>> trying to run guix system reconfigure. It failed on two different
>>>>> machines with the same backtrace. Please see the full backtrace
>>>>> attached. The error message from it:
>>>>>
>>>>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>>>>> Git error: object not found - no match for id
>>>>> (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
>>>>>
>>>>>
>>>>> $ guix describe
>>>>> Generation 28   Sep 23 2023 19:30:36    (current)
>>>>>    guix 4f35ff1
>>>>>      repository URL: https://git.savannah.gnu.org/git/guix.git
>>>>>      branch: master
>>>>>      commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016
>>>>>
>>>>> Considering that I experience it on two guix machines with
>>>>> different
>>>>> system configurations, I assume that there is some bug somewhere.
>>>> Experiencing the same for commit
>>>> 35fd25af9bbcce84908101a9f487ba106a8d6df7.  I would hazard a guess
>>>> that it's due to them being merge commits.  Interestingly,
>>>> allow-downgrades does not have an effect on this message.
>>>>
>>>> Cheers
>>>
>>> I reconfigured two machines using commit
>>> 4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
>>> machines, I didn't get this "no match for id" issue.
>>> That's strange...
>> Do you have provenance tracking on your machines (the default)?
> 
> Yes. I use an additional channel, not only the "guix" default channel.
> Maybe that makes a difference...

Also reporting similar issues on a Guix machine with multiple channels.

In my case, I have a local 'file://...' channel that I use for 
development, and have found that the following sequence of actions will 
consistently exhibit the above behavior on guix master:

1. Commit update to local channel git
2. guix pull
3. sudo guix system reconfigure

The issue is resolved by removal of the root user's guix cache in 
/root/.cache/guix (forcing a full fetch during system reconfigure), but 
repeating the above steps will cause the issue to reoccur.

I suspect it might have to do with the recent changes made to the 
'reference-available?' function in 
6d33c1f8061e86d63ab5c9ec75df9c58130c7264 (though it's not entirely clear 
why that change would cause this failure).

After downgrading my "guix" channel to 
f45c0c82289d409b4fac00464ea8b323839ba53f (the commit immediately prior 
to the above change) I am again able to receive changes from my local 
channel without issue.

Message #32 received at 66169 <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: Roman Riabenko <roman <at> riabenko.com>, 66169 <at> debbugs.gnu.org, Liliana
 Marie Prikler <liliana.prikler <at> gmail.com>, Guillaume Le Vaillant
 <glv <at> posteo.net>
Subject: Re: bug#66169: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Mon, 25 Sep 2023 12:25:20 +0200

Hi,

On Sat, 23 Sep 2023 at 22:02, Roman Riabenko via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:

> Backtrace:
> In guix/ui.scm:
>   2286:10 19 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
>   1752:10 18 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/status.scm:
>     859:3 17 (_)
>     839:4 16 (call-with-status-report _ _)
> In guix/scripts/system.scm:
>    1278:4 15 (_)
> In ice-9/boot-9.scm:
>   1752:10 14 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/store.scm:
>    659:37 13 (thunk)
>    1298:8 12 (call-with-build-handler #<procedure 7f20532e8b40 at g…> …)
>   2168:25 11 (run-with-store #<store-connection 256.99 7f2057bfd410> …)
> In guix/scripts/system.scm:
>   1302:15 10 (_ _)
>     831:5  9 (perform-action reconfigure #<<image> name: #f format:…> …)
> In guix/scripts/system/reconfigure.scm:
>     346:3  8 (check-forward-update _ #:current-channels _)
> In srfi/srfi-1.scm:
>    691:23  7 (filter-map #<procedure 7f205894eba0 at guix/scripts…> . #)
> In guix/scripts/system/reconfigure.scm:
>    353:39  6 (_ #<<channel> name: guix url: "https://git.savannah.gn…>)
> In guix/git.scm:
>    481:21  5 (update-cached-checkout _ #:ref _ #:recursive? _ # _ # _ …)
>    367:15  4 (reference-available? _ _)
> In git/commit.scm:
>     172:8  3 (_ #<git-repository 24fd030> #<oid 4f35ff1275e05be31f5d…>)
> In git/bindings.scm:
>      77:2  2 (raise-git-error _)
> In ice-9/boot-9.scm:
>   1685:16  1 (raise-exception _ #:continuable? _)
>   1685:16  0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Git error: object not found - no match for id (4f35ff1275e05be31f5d41464ccf147e9dbfd016)

This part:

    In guix/git.scm:
       481:21  5 (update-cached-checkout _ #:ref _ #:recursive? _ # _ # _ …)
       367:15  4 (reference-available? _ _)

rings this bell 6d33c1f8061e86d63ab5c9ec75df9c58130c7264.  Hum, indeed
my bad, I missed a corner-case, reviewers too, and the patch had been in
the tracked for weeks.  Arf. :-)

Well, I guess it is now fixed by
94f3831e5bb1e04eeb3a0e7d31a0675208ce6f4c.

Maybe another discrepancy is still around.

Does the usual “guix pull && guix system reconfigure” work?

Cheers,
simon

Message #37 received at 66169-done <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: Roman Riabenko <roman <at> riabenko.com>, 66169-done <at> debbugs.gnu.org, Liliana
 Marie Prikler <liliana.prikler <at> gmail.com>, Guillaume Le Vaillant
 <glv <at> posteo.net>
Subject: Re: bug#66169: guix reconfigure error no match for id
 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Wed, 11 Oct 2023 16:12:23 +0200

Hi,

On Mon, 25 Sep 2023 at 12:25, Simon Tournier <zimon.toutoune <at> gmail.com> wrote:

> Well, I guess it is now fixed by
> 94f3831e5bb1e04eeb3a0e7d31a0675208ce6f4c.

Closing.

Let me know if another discrepancy is around.

Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.