Changes in Project Files Not Detected Automatically in GitButler (Stable and Nightly)

[cuervolu]

Version

0.5.855

Operating System

Linux

Distribution Method

AppImage (Linux)

Describe the issue

Since recent updates, both the stable (0.13.8) and Nightly (0.5.855) versions of GitButler are failing to detect changes made to project files automatically. I have to manually reload the view each time to see updates. Additionally, the toolbar is missing in the Nightly version, so I am forced to use CTRL + R to refresh. This behavior does not occur in the stable version, but even there, changes are not detected until a manual refresh.

I have provided a quick video example showing the issue, though this problem also occurs with larger file changes.

https://github.com/user-attachments/assets/3eb91e97-cb2b-4564-919a-61af82df3bd5

I have tested different file changes and reloaded multiple times, but the automatic change detection remains unreliable.

How to reproduce

1. Open GitButler.
2. Make any changes to your project (small or large).
3. Observe that GitButler does not detect the changes automatically.

Expected behavior

In previous versions, GitButler detected file changes immediately. I believe this should still be the case unless there is a specific reason for the new behavior (which I'd appreciate clarification on). It's inconvenient to reload the page manually for every minor update.

Relevant log output

No response

[Byron]

Thanks a lot for reporting!

On MacOS, trying 0.13.7, 0.13.8 and nightly 0.5.855 I was unable to reproduce the issue on MacOS. Reeling in @ndom91 who will probably already have an idea what changed between these releases.

[cuervolu]

Any updates on this? The error is still present in the latest stable and nightly versions, though it occurs less frequently.

[ndom91]

Hey sorry missed this one.

So I've been using the appimage for months and I've run into this issue with every version as far back as I can remember unfortunately.

Do your changes always not get picked up? Or does it work for a while but then at some point stop picking up changes? In my case it works like the second example, the file watcher usually works for a bit, but then stops.

Anyway, we're aware the file watcher could use some more love, we've put up an issue to track it generally here: https://github.com/gitbutlerapp/gitbutler/issues/4713

[cuervolu]

Yes, it happens like the second option. Sometimes, when I make a commit or a pull request, only then does it realize there were other changes.

Anyway, I'll pay closer attention to that issue, although it's true that AppImages are often quite complex, so I'm not surprised this happens.

[ndom91]

Yes, it happens like the second option. Sometimes, when I make a commit or a pull request, only then does it realize there were other changes.

Anyway, I'll pay closer attention to that issue, although it's true that AppImages are often quite complex, so I'm not surprised this happens.

As a bit of a workaround, I noticed that certain actions in the app cause the file watcher to sort of refresh. For example, if I change default branches it usually picks up any changes (across all applied branches).

[JulianDeal]

I have the same problem on Windows right now. I tested it with Mac first, it worked. Then I installed it on Windows. It took a while on both systems to plow through all the error messages when there was active work. But no changes are detected. Not even when changing the base branch, editing files, or anything.

Tested with both 17.6 and 18.0.

[Byron]

Thanks for sharing! Does the repository live on a non-local disk by any chance? I'd love to understand what could be causing this on Windows, as this doesn't trivially reproduce whenever I test for that (on Windows or Linux).

PS: If you are interested in debugging this and are able to run the Rust toolchain, I'd have some commands for testing that just see how/if the file watcher is working.