Background backup causes continuous refreshing of Uncommitted changes view
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
Periodically, when using Gittyup, I have noticed the "uncommitted changes" view to start refreshing uncontrollably. Every few seconds (usually about 1 to 2 seconds) it would completely refresh the view and scroll the view of changes to the top. This made the app relatively unusable. Sometimes this would go on for many minutes and restarting the app would not fix it. Eventually it would stop doing it. However, while this odd behavior is happening, if I switch to different repository, the behavior stops. If I switch back, it will pick up again. It has not been consistent as to which repositories it happens with.
I suspected that something must be touching the file system and triggering a refresh but I could not see any files being changed. And the behavior continued even after I had shut down all other IDEs, debuggers and apps that might be touching files in that directory.
Eventually through process of elimination I identified that it appears to be the background backup application (BackBlaze) that is used on that system that seems to be responsible for this behavior. When I pause BackBlaze, the behavior immediately stops. When I restart it, after some time it starts doing the annoying refresh again.
I believe this is what is happening:
The background backup is set in "continuous mode" so it is not backing up on a schedule. When I start developing in a directory, a bunch of files get touched (most of them not actually tracked by git) and at some point the backup program starts processing those. At that point, something is triggering Gittyup to start continuously refreshing that view, even though at that point, I am not making any changes.
This is happening under Windows 11
Gittyup v1.2.2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source files or tests. Reproduce the uncommitted-changes refresh on Windows 11 with BackBlaze running and paused, then trace the refresh behavior; done means background backup activity no longer causes continuous refreshing or scrolls the view to the top.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100