Yeah, but it doesn’t make sense to the file name of the file to be uploaded to have any sort of influence over the process, since the models have specifically a name to identify them. Moreover, if those files remain present on the server, but inaccessibile through the api, it’s a bug in any case, I’d say

was thinking that would delete the old weights from the file server once they get updated,

If you are uploading it to the same Task, make sure the model name and the filename is the same and it will override it (think filesystem filenames)

but they are still there, consuming space. Is this the expected behavior? How can I get rid of those old files?

you can programatically also remove (delete) models None

Hi @<1792727007507779584:profile|HollowKangaroo53> , if you only want to delete old checkpoints you would need to write some automation for that. I'm guessing that the cleanup example can be a good baseline. Then just fetch the artifacts list from tasks and use StorageManager to delete the relevant files from the files server.

I don’t thinks it’s possible : the checkpoints are output models, and such can be accessed from the task, but from the model class I can get only the url of the last version (as I expected from using update weights, as it does sound like it replaces the old weights with the new ones). Also, even if I could get the urls of the old checkpoints, how can I delete them from the file server? StorageManager doesn’t seem to have any method to delete remote files