Skip to content
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.

Rar Parsing Occasionally Overflows Release Size Column #302

Closed
NeilBetham opened this issue Nov 16, 2016 · 3 comments
Closed

Rar Parsing Occasionally Overflows Release Size Column #302

NeilBetham opened this issue Nov 16, 2016 · 3 comments

Comments

@NeilBetham
Copy link

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.

@gkoh
Copy link
Contributor

gkoh commented Nov 16, 2016

This looks like #280 as the primary cause.
Of course, doing a size check is a good defense against other unknown weird stuff in our rar library.

@brookesy2
Copy link
Collaborator

@gkoh Was just going to say this looked like what you mentioned earlier :) Thanks for chiming in!-

@NeilBetham
Copy link
Author

Ah, sorry for the dupe. I will close this and move discussion to the other bug.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants