2 bug: (Is it bug? 🤔 )
when choosing "last commit in branch" field "Branch" automatically filled by "origin/Branch_name"
and when checkout it tries to checkout to branch "origin/origin/Branch_name"
` Using cached repository in "/home/achirkova/.clearml/vcs-cache/cascadeurml.git.dd4d49a1c460b395a49eb72d51f94a03/cascadeurml.git"
2021-03-05 17:00:31
error: pathspec 'origin/origin/CSC-6609_splitting_skeleton' did not match any file(s) known to git
Repository cloning failed: Command '['git', 'checkout', 'origin/origin/CSC-6609_splitting_skeleton', '--force']' returned non-zero exit status 1.
clearml_agent: ERROR: Failed cloning repository.

1. Make sure you pushed the requested commit:
   (repository='git@gitlab.nekkimobile.ru:csc/cascadeurml.git', branch='origin/CSC-6609_splitting_skeleton', commit_id='', tag='', docker_cmd='', entry_point='src/projects/autoposing/new/clearml_pipeline/task_1_create_base_dataset.py', working_dir='.')
2. Check if remote-worker has valid credentials [see worker configuration file]
   Jump to end `

No, it fails
error: pathspec 'origin/origin/CSC-6609' did not match any file(s) known to git

Hi RobustHippopotamus53 , I think this it just the place to ask this, we are all ClearML users here 😉 Let me ask you this - did you merge and also push? When I forget to push after merging a PR I think this is the same error message I get.

Hi RobustHippopotamus53
The way "latest from branch" works:
On the Task you specify the branch name (e.g. "master", no need to add the origin/ prefix) The agent then pulls the latest commit from that branch and updates back the Task to the current commit ID (the latest on the branch at the time of execution) This process ensures reproduciblity and traceability as we can always be certain the exact commit that was executed.Could it be the you "forced-push" a commit/squash, hence the "original" commit ID does not exist anymore ?

What about cloning and setting "last commit in branch" ?

No, seems like unrelated
1 bug: can't checkout to some branch if master was changed
steps:
commit and push Branch_A run Task_A locally to init it merge master branch with Branch_B via gitlab's "Merge Request" create clone of Task_A via Web and enqueue agent clones master without errors but fails when checking out to Branch_A` done.
cloning: git@gitlab.nekkimobile.ru:csc/cascadeurml.git
2021-03-05 13:56:50
Filtering content: 100% (3180/3180), 9.10 GiB | 10.48 MiB/s, done.
2021-03-05 13:57:40
fatal: reference is not a tree: 0e6761fd7dbb447fd26871723d9d61eb33836783
Repository cloning failed: Command '['git', 'checkout', '0e6761fd7dbb447fd26871723d9d61eb33836783', '--force']' returned non-zero exit status 128.
clearml_agent: ERROR: Failed cloning repository.

1. Make sure you pushed the requested commit:
   (repository='git@gitlab.nekkimobile.ru:csc/cascadeurml.git', branch='origin/CSC-6609_splitting_skeleton', commit_id='0e6761fd7dbb447fd26871723d9d61eb33836783', tag='', docker_cmd='', entry_point='src/projects/autoposing/new/clearml_pipeline/task_1_create_base_dataset.py', working_dir='.')
2. Check if remote-worker has valid credentials [see worker configuration file] `

Yes, merge was done via gitlab merging request (not by me)

Okay so sounds like two bugs stacked together? I wonder if this is gitlab specific. Could you provide a list of a steps to reproduce? 🙏

Seems like I have to just remove "origin/" (it automatically set full path) from "Branch" field when choosing "last commit in branch"

It works! I just commit and push some dummy changes in "my_brach"
Although it fails when trying to run clone of newly created "my_task" (or reseted) without some new commit of "my_branch"