I run model training for weeks, where I train hundreds of models with different hyperparameters. Therefore, I need automatic naming of newly created tasks. Maybe there are some examples of how to set custom task naming scheme?

I don't know if this will always work.
You have correctly describe my issue. How does ClearML select reference branch? Could it be that ClearML only checks "origin" branch?

For Task creation I am using Task.init in my code. Due to documentation it should make "A link to the running git repository (including commit ID and local uncommitted changes)", however it chooses another repository.

If I manually enter credential keys after specifying the Web server it continues sending a request to port 8008.

AgitatedDove14 Exactly

$ git ls-remote --get-urlalso returns Gitea url.

Here is an issue https://github.com/allegroai/clearml/issues/516 .

AgitatedDove14  
Stackoverflow says about the size of the file name, but here the problem is with the size of the folder name. Not sure if the file and folder limits are the same. The error that occurs says that An error occurred (XMinioInvalidObjectName) when calling the CompleteMultipartUpload operation: Object name contains unsupported characters. . At first I thought I was using the wrong characters in the task title, such as backslash, colon or space. But I managed to upload model...

Maybe it makes sense to limit or change number of parameters which participate in name generation or allow users to use their own naming scheme. https://github.com/allegroai/clearml/blob/24464b7c1019f7a7b3149ecb80a379c5f82337a0/clearml/automation/optimization.py#L720

It returns Gitlab url as it is pinned to origin.
$ git ls-remote --get-url giteareturns Gitea url.

Maybe you should make naming_function as public variable in SearchStrategy class or allow changing it in HyperParameterOptimizer class?

I came up with a workaround to solve this problem, but since I run tasks remotely, where not my modified clearml code is used, this problem will remain until you fix it. Should I duplicate this issue in the github?

Is it possible to change the port for API server? I tried replacing ports in apiserver section in docker-compose.yml.
ports: - "8008:8011"But it didn't help. Now curl http:/10.68.167.10:8011 does not work from the host machine.

Nice, curl http:/10.68.167.10:8011 now works. But in credentials creation it still shows 8008. Are there any other places in docker-compose.yml where port from 8008 to 8011 should be replaced?