ok, i got the problem, it isn't really related to spaces or local vs remote. It is the presence of characters like
! . Indeed the artifacts on GCS are created converting
%21 and are tracked succesfully like this on the server. When the request is sent to actually download the artifacts or to see pictures in Debug samples the
%21 is converted back to
! and there is no such object in GCS with
! . Hope it's clear. Not a big deal to me, can just avoid special characters. 🎉
Cloud Access section is in the
Any storage credentials (S3 for example) are only stored on the client side (never the trains-server), this is the reason we need to configure them in the trains.conf. When the browser needs to access those URL's (downloading an artifact) it also needs the secret/key, it automatically display a popup requesting them, and will store them in this section. Notice they are stored on the browser session (as a cookie).
When the Task is executed on a worker, the presence of spaces breaks the URLs and from the UI I cannot access to the resources on the bucket
You are saying the URLs generated in a remote execution are "broken" and on local execution are working, even though it is the same project/task name ?
Whats the exact project/task name?
And what is the output_uri?
task_name="Run from CD + FS"
the output_uri isn't set, but the fileserver is set to the GCS location in
trains.conf and indeed the artifacts and the metrics are correctly stored where supposed to be
what i can say is that when tasks are running locally the task name can have spaces, when executed remotely they cannot. I tired to remove the spaces in a remote execution and the artifacts are linked without problems (in both cases they are created just fine on GCS, it's just a matter of linking them in the Server UI)