Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
I’M Trying To Clone A Task That Had Cloned My Code Using A Github Access Token That Is Now Expired. I Updated To A New Token In

i’m trying to clone a task that had cloned my code using a github access token that is now expired. i updated to a new token in clearml.conf , and restarted my agent, but the console shows that the old token is still being used for some reason. is there any way I can make the cloned task use the new token?

  
  
Posted one year ago
Votes Newest

Answers 33


We always aim to improve 🙂

  
  
Posted one year ago

thanks for that tip. i cleared out the vcs cache and was already using the latest version of the agent, same problem persists.

there’s a python version mismatch, i will make a different env for the agent to run in that has a matching python version

  
  
Posted one year ago

How did you update the new token?

  
  
Posted one year ago

agent version is

❯ clearml-agent --version
CLEARML-AGENT version 1.5.2
  
  
Posted one year ago

so now i have

git_pass: "[NEW KEY]"
enable_git_ask_pass: false

in my clearml.conf file

  
  
Posted one year ago

yes. had to sanitize it a bit, but left the git username/key intact (since the key is invalid now)

sorry for the delay, had work and personal emergencies 😕

  
  
Posted one year ago

the VCS cache was empty before that run. then, even with the VCS cache being disabled in the config, there was a new lock file and directory after running.

  
  
Posted one year ago

there were env variables set in .zshrc

  
  
Posted one year ago

i don’t get why the agent init log would list the username from clearml.conf but then use the env vars

  
  
Posted one year ago

That's probably an issue we should look at

  
  
Posted one year ago

weird. will move forward with manually recreating the task.

  
  
Posted one year ago

Can you try to change the username as well and see if the agent uses the new one?

  
  
Posted one year ago

further, there’s now data in the VCS cache, even though i disabled it

  
  
Posted one year ago

  • stopped agent
  • updated clearml.conf to have different username, wrote file
  • verified the vcs-cache is empty
  • started the agent, which resulted in this output
...
agent.custom_build_script =
agent.disable_task_docker_override = false
agent.git_user = aaaaaaaaaaaaa
agent.default_python = 3.9
...

(that’s the username I changed it to)

  • reset and enqueued the task
    checkout failed, it’s still attempting to use the old creds
  
  
Posted one year ago

i meant I should have thought to check there earlier! anyway, thanks again for your attention and help! 🙂

  
  
Posted one year ago

Can you share the agent log, specifically when it's trying to clone?

  
  
Posted one year ago

Also, are you sure you cleaned the VCS cache? There's no other place the agent can get the old token from...

  
  
Posted one year ago

Hmmm. Just tried cloning a brand new task and the agent is still using the expired github access token.

  
  
Posted one year ago

Yes, it does. What setting in the file did you use? git_pass ?

  
  
Posted one year ago

thanks much for your help. should have thought to check there earlier, but kind of forgot that was a thing.

  
  
Posted one year ago

yes

  
  
Posted one year ago

also tried disabling the VCS cache in the config—pull this from the output of the agent’s startup output:

agent.vcs_cache.enabled = false
  
  
Posted one year ago

❯ cat ~/clearml.conf | grep git_user
    git_user: "aaaaaaaaaaaaa"
❯ cat ~/clearml.conf | grep -A 2 vcs_cache
    vcs_cache: {
        enabled: false,
        path: ~/.clearml/vcs-cache
  
  
Posted one year ago

:face_palm:

  
  
Posted one year ago

the clearml.conf used by the agent?

  
  
Posted one year ago

if i run clearml-agent daemon that reads from ~/clearml.conf , right?

  
  
Posted one year ago

Hi @<1523712386849050624:profile|NastyFox63> , I assume this is the vcs cache storing the old token (this is probably an older agent version as this has been fixed in recent versions). I suggest clearing the vcs cache of the agent (should be under ~/.clearml) and upgrading the agent version

  
  
Posted one year ago

yes—am running the agent on a workstation. am sshed into that workstation and verified the change in the conf by explicitly disabling the VCS cache and then looking for that in the agent’s startup output

  
  
Posted one year ago

restarted the server on the off chance that had anything to do with it, and no. VCS is disabled, and the task is trying to pull the correct/latest commit.

  
  
Posted one year ago

Just checking again, can you delete the vcs cache?

~/.clearml/vcs-cache

Also, make sure this is turned on:
None

  
  
Posted one year ago
45K Views
33 Answers
one year ago
one year ago
Tags