Linux Appimage cant delete branches

[KroniK907]

Version

0.15.19

Operating System

Linux

Distribution Method

AppImage (Linux)

Describe the issue

Attempting to delete any branch seems to hang all branch management related actions in the application. Once I attempt to delete a branch, the red delete button sits there with a spinner icon forever with seemingly no effect. If you click cancel or click outside the dialog box, the create branch flow similarly hangs when attempting to create a new branch. It takes a full restart of the application to fix this issue. Nothing shows up in any logs that I can find.

Attached is a video showing the behavior. I launched the app from the command line so you can see the log output at the bottom of the recording. I also am showing the developer settings console. Nothing seems to appear when I attempt to delete the branch.

gitbutler-delete-branch-issue.mp4

How to reproduce (Optional)

1. Create a branch
2. Attempt to delete the branch
3. The branch does not delete and any future branch creation is also broken.

Expected behavior (Optional)

No response

Relevant log output (Optional)

[KroniK907]

Maybe related to #8275?

[KroniK907]

As an interesting addendum, It looks like the delete branch actions are logged in the operations history page, even though the branches were never actually deleted.

[Byron]

Thanks a lot for reporting, this is a very interesting issue!

The creation of the snapshot happens before the actual deletion, but it's incredibly strange that there is nothing in the logs even. I'd expect one line to be printed when the function is entered, and it's clearly entered as the snapshot is created.

My guess here is that somehow the IO of branch deletion is hanging forever, and you'd be able to see that with strace I presume if you wanted to take a closer look. Also, I am assuming there is no high-CPU.
Oh, another reason this could happen is if it panics - did you start the application from a terminal? If so, panics would show up there (it's different from tailing the logs). Maybe we could take another look to exclude panics.
Thanks again.

[KroniK907]

I did launch it from the terminal, so what you see in the terminal window at the bottom is just the Standard Out and should have shown the panic. I'm not sure where to find the actual log files. I'd be happy to tail the log and see if I can find something there.

I tried looking for logs in the following directories as mentioned in the documentation but im not finding any logs there.

~/.config/gitbutler/logs/        [OR]
~/.local/share/gitbutler-tauri/logs/

Is there an easy way to get the app to tell me where its putting logs?

Since our timezones dont line up well, I went ahead and used the "Share Debug Info" system in the app to send the logs over after trying to delete a branch several times. I referenced this github issue in the dialog box when I sent the logs.

[Byron]

Thanks for the clarification.

I did launch it from the terminal, so what you see in the terminal window at the bottom is just the Standard Out and should have shown the panic. I'm not sure where to find the actual log files. I'd be happy to tail the log and see if I can find something there.

Then there is no need for logs, stdout/stderr will already show everything, including panics. For completeness, the logs can be found here.

Thanks for the sharing the debug information! Usually it doesn't find it's way to me as I have no access, but I will request it if I think these will be useful. For now I think I have everything.

Something you could do is to launch the app with debug logging enabled like this:

LOG_LEVEL=debug /path/to/gitbutler-tauri

When deleting a branch I'd expect to see remove_branch in the terminal, and probably it never finishes. Actually, this should be INFO level so it should have been visible before, but nothing seems to have been visible.

Lastly, could you open the developer tools via View -> Developer Tools and check the networking tab for remove_branch? My guess is that it never finishes.

If that is true, then strace will show where it's blocked.

Thanks again.

[jeyj0]

Just FYI, this happens on the .deb version too, but only applies to branches that are being depended on, or that have no commits.

Currently don't have the time for further investigation, but will follow the suggested steps if I do find the time at some point.

[lakshya-singh-glean]

I also tried it can't get a single log even with debug on

[Byron]

@lakshya-singh-glean Was the application launched from the terminal? If so, it would be very surprising for no log to show up - even without any other environment variables a lot of INFO logging will be visible.

[king-11]

INFO is visible but there weren't new logs being emitted when I clicked delete. The UI never really felt like click does something. and TRACE was too much for me to parse myself but can get a file of logs if needed