Sebastian Thiel

Thanks for reporting! The filesystem probe would be thread-safe (within the worktree-state test-suite) now and I would expect it to be stable - that I have now put to the...

My *feeling* here is that the file watcher triggers an operation which should be read-only, but isn't. Then the operation changes some Git state, maybe it fails doing so, just...

Thanks a lot! I took a look at the lock and fortunately do not see signs of a loop due to filesystem events. A lot happens, and there is plenty...

Thanks for reporting. A flatpack binary is very sandboxed, and I have a feeling that frontend/backend communication isn't working correctly. As a note I may add that I saw the...

Thanks a lot, I think that's helpful! I don't know if it's compounding the issue visible here, but from the logs it seems to have trouble getting anything useful from...

Apologies for the ambiguity - that's exactly what I mean, rename it to something else and restart GitButler to see if fresh metadata does the trick.

Thanks a lot, I am glad it's 'fixed'! Maybe you could run one more experiment, put back the broken version, and rename just the `projects.toml` file inside of that directory....

Oh, apologies, and thanks so much for your help! Indeed it's a `projects.json` file, and not a toml. And indeed I would have expected that this folder is recreated, and...

That directory contains all shared data - each project then has a `.git/gitbutler` directory as well. However, when the shared data is gone, it looses all information about added projects,...

Thanks for sharing! Somehow I feel there are two issues at play here - general issues around hardware acceleration, and others about an invalid state on disk that prevents the...