Mohammad Bakir

@maxzw, thank-you for writing in. This bug is still being addressed. We will update the community here once a fix has been implemented. Regards

@mukobi , @Jiuzhouh, @jxmorris12, @abhinav-kashyap-asus. Thank you for the continued follow up on this and our apologies that it got buried. We are going to revisit, but would appreciate your...

Hi @konatasick if you have no data to worry about, delete the image and volume first then retry ``` docker stop wandb-local docker images -a docker rmi docker volume rm...

Hi @erhlloyd, happy to help and we appreciate you writing in with your question. As per our email response from earlier today, here's a [SQL procedure](https://gist.github.com/vanpelt/0c13c556fa82cabdecb70d5ef90a4ea9) that will delete the...

Thank you for the update @erhlloyd, looping in @vanpelt for consideration/review of feedback to the pruning script.

Hey @erhlloyd , since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!

Hi @EricWiener, I wasn't able to identify which files/folders @adizhol deleted from review of their posts. The statement **(from scratch)** reads to me as deleting their entire docker image/container and...

@rakesh-sodha , Thank you for providing info. We will attempt to reproduce. I did a search online to see if there are any known issues with `iTerm cmd` and a...

Hi @longzilicart , thanks for writing in and happy to help. I'm going to ask internally on if there is a recommended W&B approach to resolving this and get back...

Hi @longzilicart , spoke to our deployment team and as it is difficult to isolate the specific reason why your DB became corrupt, we cannot guarantee the below will provide...