{"meta":{"id":"3b79f199a7fa42db8a30abbc67adbaa3","trx":"3b79f199a7fa42db8a30abbc67adbaa3","endpoint":{"name":"","requested_version":1.0,"actual_version":null},"result_code":400,"result_subcode":0,"result_msg":"Invalid request path /","error_stack":null},"data":{}}

done

try: trains-init config

the code doesn't work

No that's okay

Are the key/secret the one you see in the UI?

yep. they are

thanks. it seems to work now.

we are still considering whether to upgrade or not.

if it ain't broke, don't fix it

I logged in to the UI from the local browser. is that enough?

trains-init: error: unrecognized arguments: config

yes its the JWT issue

i.e. you can:
curl

that's the result

we have a cloud machine running the server UI and I want to log sessions from my local machine

Any reason not to ?

pip install "pyjwt<2.0.0"

make sure the API port is 8008 and the web 8080

And the server itself? is it http or https ?

TRAINS-AGENT setup process
Configuration file already exists: ~/trains.conf
Leaving setup, feel free to edit the configuration file.

http

my UI is also deployed on http server

Same machine running the trains-init ?

jwt.exceptions.DecodeError: It is required that you pass in a value for the "algorithms" argument when calling decode().

if it ain't broke, don't fix it

😄

Up to you, just a few features & nicer UI.
BTW: everything is backwards compatible, there is no need to change anything all the previous trains/trains-agent packages will work without changing anything 🙂
(This even includes the configuration file, so you can keep the current ~/trains.conf and work with whatever combination you like of trains/clearml on the same machine)

Just making sure, the machine that you were running the "trains-init" on can access the API server ?

Everything seems correct...
Let's try to set it manually.
create a file ~/trains.conf , then copy paste the credentials section from the UI, it should look something like:
api { web_server: http:127.0.0.1:8080 api_server: http:127.0.0.1:8008 files_server: http:127.0.0.1:8081 credentials { "access_key" = "access" "secret_key" = "secret" } }Let's see if that works

BTW: I think it was fixed in the latest trains package as well as the cleaml package

Ohh

yes