When tabby is running, unstaged git changes are randomly reverted/dismissed

[ragauskl]

Describe the bug
After some time of using tabby for autocomplete in VS Code, any unstaged modifications for those files that already exist on indexed branch get dismissed (I'm on version branch, when develop branch using file:// is the one that's indexed in Tabby dashboard), but any new untracked files remain. I got a scare when this happened unexpectedly but luckily VS Codes 'Local History: Find Entry to Restore' saved me, just had to do it for bunch of files one by one.

I checked git and no git commands were executed at all near that timeframe when issue occurs. I have followed the setup from tabby webpage and use local model qwen2.5-coder:7b-base for kind ollama/completion. Everything works fine besides this random reset of unstaged modifications.

There is an error in Tabby logs around that time: (node:19596) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 newAttached listeners added to [cx]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit

Also around the time it happens I see in Windows Process Monitor WriteFile from tabby.exe, then by 'System' and multiple reads from rg.exe which all stick out from the usual pattern of events that happen during normal editing/using autocomplete and saving in VS Code.

Information about your version
0.32.0

Information about your GPU
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 596.36 Driver Version: 596.36 CUDA Version: 13.2 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Driver-Model | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 5080 WDDM | 00000000:01:00.0 On | N/A |
| 0% 40C P3 36W / 360W | 8164MiB / 16303MiB | 1% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+

Additional context
OS: Windows 11
Running tabby just in Windows terminal for now
VS Code Extension version: 1.28.0

No other similar extension/process was running at the time of the issue, I have initially installed 'continue' but while I'm testing tabby I have disabled the rest.

Will try to monitor and see if I can find anything else

[ragauskl]

If I stage changes before continuing to work until the issue occurs again, all changes including untracked files get reset/lost. I crossed out rg.exe as it did not appear this time, only writes from tabby.exe and one from System. This time it happened on file save and there's no additional MaxListenersExceededWarning

[ragauskl]

Seems to just happen on it's own, left it open on the side without making any changes to the project, the events in screenshot are filtered for one specific file (any with uncommited change would do)

tabby logs don't show anything of interest, just usual empty codelens log

All events that happened within this timeframe, not sure what else to check

I assume tabby is treating file:// context provider as ~/.tabby/repositories/ ? I'm just not sure if that's how it's intended and just not mentioned in the docs, I would assume even if pointing to file:// it should not override local changes? Or if using file:// we need to keep second local repository for that?

[wsxiaoys]

Thanks for reporting the issue - yes file:// is treated as a local repository just like how we treat ~/.tabby/repositories, thus tabby server itself doesn't expect the path being a readonly snapshot rather than an working repository

[ragauskl]

Is there any way to make it treat file:// as a readonly access and make its own clone to /repositories?

Is this generally mentioned somewhere in the docs (can't find it if it is, maybe I'm misreading something) or it's the expected way for this to work like that (I just started messing with local LLM setups first time, so I may be slightly clueless)?

[ragauskl]

I guess this #1218 (reply in thread) is the closest I found to mentioning this, but even then it says 'reads' not overwrites/resets

Would be nice if this was mentioned in the docs especially for first time setups