Well, since the WebApp sends the delete request to the fileserver, you can try deleting another experiment and monitoring the requests sent by the WebApp in the developer tools Network section
Oh, sorry, I thought you meant you can delete them 🙂
I can also access these files directly if I enter the url in the browser
You mean using a DELETE request?
I can also access these files directly if I enter the url in the browser
I could delete the files manually with sudo rm (sudo is required, otherwise I get Permission Denied )
/opt/clearml/data/fileserver does not appear anywhere, sorry for the confusion - It’s the actual location where the files are stored
These images are actually stored there and I can access them via the url shared above (the one written in the pop up message saying that these files could not be deleted)
Do you simply mean these images are actually stored there? or does it appear in any of the responses?
Oh, OK, so where exactly does /opt/clearml/data/fileserver appear?
SuccessfulKoala55 They do have the right filepath, eg:https://***.com:8081/my-project-name/experiment_name.b1fd9df5f4d7488f96d928e9a3ab7ad4/metrics/metric_name/predictions/sample_00000001.png
JitteryCoyote63 what are the exact URLs you received? The WebApp is the entity sending the delete requests for uploaded objects (as they are handled by the fileserver, usually, and only registered in the server). However, I would expect those to have a fileserver URL (i.e. something like http://<host-name-or-ip>:8081/path-to-file ) and now a direct file path