Hi @<1523708920831414272:profile|SuperficialDolphin93> , once you deleted the cache folder did it work?
Also, did you try pulling the specific commit using the same credentials that are defined on the agent machine?
Hello,
When sending new tasks using python script, I'm getting this error no matter how many times I retry the task, even though the commit is pushed and the agent has correct credentials. I figured out the problem is the cached repository because the error disappears when I manually delete the cached git repository.
Using cached repository in "/home/neurohelp/.clearml/vcs-cache/neurohelp-innovation-conv-lstm.git.249bc385aa8001d5ccb927a5e47e3011/neurohelp-innovation-conv-lstm.git"
pulling git
error: insufficient permission for adding an object to repository database .git/objects
fatal: failed to write object
fatal: unpack-objects failed
error: Could not fetch origin
git pull failed: Command '['git', 'fetch', '--all', '--tags', '--recurse-submodules']' returned non-zero exit status 1.
Repository cloning failed: Command '['git', 'fetch', '--all', '--tags', '--recurse-submodules']' returned non-zero exit status 1.
clearml_agent: ERROR: Failed cloning repository.
1) Make sure you pushed the requested commit:
(repository='
', branch='master', commit_id='9fb133a1d6c843d521b2f347d1dff1c77502a898', tag='', docker_cmd='nvidia/cuda:12.8.1-runtime-ubuntu22.04', entry_point='scripts/ignite/train_ignite.py', working_dir='.')
2) Check if remote-worker has valid credentials [see worker configuration file]
The cached repository is a few days old, not too old and maybe some files have changed, i.e. renamed, deleted or added. There is only one agent per machine so I can't understand why the repo can't be pulled.
I'm using the same clearml agent in the same user all the time.
I tried manually changing the cached .git sharing config as in this suggestions but no luck.
Any ideas why this happens and how to fix?
Hi @<1523708920831414272:profile|SuperficialDolphin93> , once you deleted the cache folder did it work?
Also, did you try pulling the specific commit using the same credentials that are defined on the agent machine?