Hi,
We had a case last week where a user managed to upload several files that resulted in the file size being 0 (completely empty). He is able to open the files locally. Mostly PDFs and within the same short timeframe, though not all the files were affected. We had some checks for files with 0 file size, but since they were outdated they didnt catch this specific case. Has not happened many times over the years, and our own checks are now up to date so it should not happen again.
I was just wondering what might cause the file to become zero bytes when uploaded, could this e.g. be affected by us deploying changes to the staging environment while the user is uploading files in the production environment?
Just trying to figure out what might have caused the files to become empty.
Hi!
To answer the last question first: Changes to staging environment while the user is uploading files in production should not affect this (individual runtime environments for these two) - except the theoretical case where some database operations meet a concurrency constraint (e.g. same object updates from staging and production, with strict object versioning enabled). Does not sound like this is the case here.
I do not know what may have caused this. Has this occurred before, or was it a one-off? Something you are able to reproduce? Anyway: Suggesting to use the support email (support@appfarmio) for further deep-dive into this, as it sounds like a solution-specific event.
I’ve had no luck in reproducing, but it seems like a rare case and might have had something to do with the users internet connection at the time or other local factors. Hopefully our preventive measures and checks eliminates this as a problem if it is to occur again.
Regardless i will reach out to support if it happens again. Thanks