-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate filewatcher edge cases (appimage, wsl, etc.) #4713
Labels
bug
Something isn't working
Comments
Would you be able to check if e.g. modifying package.json generates any activity whatsoever? I would let it idle for a bit, then tail -f -n 0 on the log file, and save the change. |
ndom91
changed the title
Filewatcher not always working inside AppImage
Investigate filewatcher edge cases (appimage, wsl, etc.)
Sep 24, 2024
There's another edge case with WSL2 users here. In that thread, @Byron had an interesting idea to test disk events ourselves on startup and if we don't get them, fallback to polling for example, more details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
0.12.20
Operating System
Linux
Distribution Method
AppImage (Linux)
Describe the issue
Edge cases:
When running GitButler via the AppImage, the file watcher sometimes does not work as expected. I then have to reload (Ctrl + R) the application to pick up changes.
I can't quite pin down how to reproduce this consistently, but i have noticed this tends to start to happen after the application has been open for a while.
Running
inotifywait -m package.json
, for example, to monitor and print inotify events on thepackage.json
file shows thatMODIFY
events are fired as expected when writing topackage.json
, but GitButler running simultaneously via the AppImage doesn't display any modified files in my default branch.How to reproduce
No response
Expected behavior
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: