fix: check if reported size is numeric in file info command#55069
fix: check if reported size is numeric in file info command#55069
Conversation
Signed-off-by: Richard Steinmetz <[email protected]>
No, it is not ... |
|
fyi #54919 |
I guess you have to ignore or add to the baseline. Or ensure that we are not returning an invalid size here. Probably it's just the data from CacheEntry forwarded without validation. |
|
Thanks, then it is fixed already. I was confused why it would print even if we check for Closing in favor of #54919. |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Summary
The stat array will contain a 'size' member if S3 is used as primary storage. However, it will be empty leading to confusing error messages:
warning: object had a size of but cache entry has a size of 59. This should have been automatically repaired(See how there is no actual size mentioned after
size of.)Checklist