SDK: v14.x.x
CLI version: v0.44.4
Python: v3.12.9
Isolation mode: venv/docker
Viktor is picking up uncommitted git changes, where there aren’t any. I’m wondering if anyone else has encountered this or has a work around.
@bvanderhulst @mozturk FYI, might be the latest CLI addition?
I suspect that the files are untracked. If you run git status you would see them in the list of “Untracked files”, is that correct? In that case, you can run git add . to add them first, as shown in the CLI message.
Thanks for your response, no such luck sadly.
I’ve been doing everything pretty much the same as I always have so surprised to see this crop up, though I will note I did do an update to my viktorCLI recently.
I am working around by updating via the file system for now.
Actually, this has become a bit of an impediment.
I’ve uploaded from the file system, but a few of my most recent uploads have been hanging / taking awhile to upload.
Feels like there was a bit of a glitch, but I’m unable to upload again until the current app version finishes uploading.
Is there a way to kill the prior upload?
The connection eventually timed out, but I’d be keen to know if there is a way to manually kill the uploading process.
I seem to be having a similar problem on GitHub actions. This has run without issues for months. Only this weekend I get the error below. I don’t think it should be necessary to include viktor-cli in the repository and I don’t want to include file.txt.
ERROR:
Exiting because of an error: uncommitted changes detected in git repository
Files with uncommitted changes:
file.txt
viktor-cli
To resolve this, you can either:
1. Commit your changes: git add . && git commit -m “Your commit message”
2. Stash your changes: git stash
3. Use filesystem mode: add --use-filesystem flag to bypass git validation
Due to the problems encountered, the latest changes were reverted. Problems should be resolved in the latest release v0.44.5.
