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
{{ message }}
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.
I've been running into some issues in post processing recently with rar parsing specifically. There seems to occasionally be issues where the parsing of a rar is overflowing the max size of a big int column in postgres. I'm not quite sure where the issue is coming from, my best guess is probably a malformed rar file. In any case the best solution I can think of is to check if the size is greater than or equal to the overflow and set it to 0; I find it very hard to believe any upload would be pushing 9 exabytes. Thoughts? If people are cool with that I can add a fix for this.
The text was updated successfully, but these errors were encountered:
I've been running into some issues in post processing recently with rar parsing specifically. There seems to occasionally be issues where the parsing of a rar is overflowing the max size of a big int column in postgres. I'm not quite sure where the issue is coming from, my best guess is probably a malformed rar file. In any case the best solution I can think of is to check if the size is greater than or equal to the overflow and set it to 0; I find it very hard to believe any upload would be pushing 9 exabytes. Thoughts? If people are cool with that I can add a fix for this.
The text was updated successfully, but these errors were encountered: