You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disk usage is not working in production; users' disk is not being accurately computed when deleting/creating bundles. for instance, see here.
It would appear the changes I made in this PR are not working properly in production.
Luckily, I can revert back to the old method of computing disk quota and it will recompute their quota (see here and, in particular, update_user_disk_usedhere, which uses a query here to just recompute the user disk quota from scratch).
In short, I can effectively revert this change for the time being and the user's disk usage will automatically be reset to their true usage whenever they next make any changes that affect disk quota (e.g. upload a bundle or delete a bundle). I will investigate why this change passed the test and seems to work sometimes (e.g. when I tested it in dev) but not at other times. I suspect there may be a race condition somewhere.
The text was updated successfully, but these errors were encountered:
Disk usage is not working in production; users' disk is not being accurately computed when deleting/creating bundles. for instance, see here.
It would appear the changes I made in this PR are not working properly in production.
Luckily, I can revert back to the old method of computing disk quota and it will recompute their quota (see here and, in particular,
update_user_disk_used
here, which uses a query here to just recompute the user disk quota from scratch).In short, I can effectively revert this change for the time being and the user's disk usage will automatically be reset to their true usage whenever they next make any changes that affect disk quota (e.g. upload a bundle or delete a bundle). I will investigate why this change passed the test and seems to work sometimes (e.g. when I tested it in dev) but not at other times. I suspect there may be a race condition somewhere.
The text was updated successfully, but these errors were encountered: