-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug: Deciding to delete non-existing model #1400
Comments
@Abellegese could you explain this a little bit more, especially this part:
Do you mean to say that the model's folder in the |
First time I ran the command and it was successfull, but when I delete same model again it says successfully deleted, and that need delete function was also True. But infact image, eos folder was mot there for the model if that makes sense. |
Thanks @Abellegese - that is somewhat making sense, however I need further clarity. Can you help me with the exact steps I could run to reproduce this? Thanks! |
@Abellegese is it somewhat related to this by any chance? |
Yeah a little bit related but mine was here maybe if you could be able to reproduce. Fetch for instance eos3b5e |
Hi @Abellegese I am still having trouble reproducing this, for example, this is what I see: ![]() I fetched eos3b5e, as you can see through the catalog output, and it has its corresponding folders in the dest and repository directories. I then deleted it, and it got successfully deleted, and then I deleted it again which raised an error, as expected. |
Hi @Abellegese Is it that you do the same procedure that @DhanshreeA is showing but then instead of saying |
This issue has been resolved when I tried latest ersilia version. I think I was kind of outdated. |
Describe the bug.
The delete cmd, when I tried to delete eos3b5e, the
needes_delete
considered that the image or model existed and considered it as it needs deletion, but the model was not there, its folder on bothdes
andrepo
.Describe the steps to reproduce the behavior
No response
Operating environment
Ubuntu LTS
The text was updated successfully, but these errors were encountered: