-
Notifications
You must be signed in to change notification settings - Fork 87
Blob coming back after few days deleting! #99
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
When you make a delete, it's removed from the file system. There's no process in place that can recover that. |
But it is returning 🥴 I don't know how. |
Here's a blob I just created and verified it returns a 404 when requesting it. I'll keep and eye on it, but I don't see a way that it can be restored...
|
Okay I'm too checking! Meanwhile here's a blob id which got restored 904641375539314688. Keys at index 1 & 2 (now) were at the time of deletion. As I deleted the blob i was getting same response as you stated above but after few days all the data came back. Maybe you can check when it was deleted and when it came back from logs. |
Hi @uraashif. I don't see anything abnormal in the logs for |
Maybe the issue is that we can still update the data of blob which is deleted in the past. I just added a key in your 993527046336692224 blob and it was successful. If blob does not exists then how can anyone update it? 😵
|
@uraashif I think you might be correct. There's no check to make sure a blob exists when a
|
Thanks, @uraashif! I'll deploy the version with the fix tonight. |
Okay!👍 |
Uh oh!
There was an error while loading. Please reload this page.
Blob is not deleting permanently for dictionaries data type. For some days after deleting it says "Blob does not exists" but later after few more days it starts existing with all the data which was saved before deleting plus adding 2 more keys in the dict at top (attached in img). Make deletion permanent for dictionaries data type. This is not happening with lists data type.

The text was updated successfully, but these errors were encountered: