exalate-issue-sync[bot]

WandB Internal User commented: chuber1986 commented: Actually, it looks very similar to #40 . Could someone figure out what waas the problem there?

WandB Internal User commented: ericxsun commented: > This likely means your database is corrupt. If you don't have any important data logged to the server, you can run: > >...

WandB Internal User commented: akashAD98 commented: https://github.com/wandb/local/issues/34 here is same issue but not able to solve

WandB Internal User commented: lesliewandb commented: Hi @liswp, I see that you opened up two tickets with the same issue. I'll respond on the[ other one](https://github.com/wandb/local/issues/102) and close this one...

WandB Internal User commented: AndreeaRadoescu commented: Ok, I will try that then. Thanks so much for all your help!

WandB Internal User commented: Jeffrey28 commented: Actually no. The latest two versions both have the same issue.

WandB Internal User commented: Jeffrey28 commented: I‘m in 0.21.0. It works only after I delete the volume. But if I try upgrading, it failed. ``` docker logs -f wandb-local ***...

WandB Internal User commented: Jeffrey28 commented: Recent versions cause me to fear upgrading

WandB Internal User commented: vanpelt commented: We understand your fear and our adding more tests to prevent upgrade failures like this in the future. 0.21.0 had a regression which caused...

WandB Internal User commented: Jeffrey28 commented: > Thanks, it works now with these two lines.