Tauri image error popup

[ukarlsson]

Version

0.13.2

Operating System

macOS

Distribution Method

dmg (Apple Silicon)

Describe the issue

This popup comes up all the time for me since recent update.

It says

f6d45a630a194830bbddb22ac1d72f91: The reference did not exist a@tauri://localhost/_app/immutable/chunks/Icon.FmaqJgaA.js:1:940 fromError@tauri://localhost/_app/immutable/chunks/Icon.FmaqJgaA.js:1:1109 @tauri://localhost/_app/immutable/chunks/Icon.FmaqJgaA.js:1:1319

How to reproduce

No response

Expected behavior

No response

Relevant log output

No response

[Byron]

Thanks a lot for reporting!

It's probably something about how the UI intercepts backend errors - previously it must have (maybe unintentionally) ignored some of the errors that occurred, while now it will show all of them.

This error in particular is well known and seems to happen when the sidebar (with branch information) refreshes. It comes from gitoxide and I think it would help if the reference it tried to fetch was mentioned.

[ukarlsson]

I still get these popups all the time but they are slightly different now

[anirudhsama]

Thanks a lot for reporting!

It's probably something about how the UI intercepts backend errors - previously it must have (maybe unintentionally) ignored some of the errors that occurred, while now it will show all of them.

This error in particular is well known and seems to happen when the sidebar (with branch information) refreshes. It comes from gitoxide and I think it would help if the reference it tried to fetch was mentioned.

For me, it tries to fetch the same branch multiple times (main in my case). See the recording: https://cln.sh/W0Wdllx7

[Byron]

That's interesting! I wonder what's happening there that master doesn't exist, at least in that very moment.
Having looked at the code, I'd think this error is genuine and not a false positive.

Something I could imagine happening here is that somehow the master branch is moved into packed-refs, and it's implemented in such a way that the loose ref is deleted before writing out the changes to packed refs. It seems absurd though and I don't think git2 would do that, or Git for that matter, nor do we use gitoxide to edit references if that should be buggy.

But at least it's a hint… as it also shows that this is about branches that GitButler usually doesn't write, I think. CC @krlvi , as I am a bit out of ideas here.