Comment #10 on issue 3660 by chip...@gmail.com: Files randomly get lost
from a review request ("This is an empty file.")
https://code.google.com/p/reviewboard/issues/detail?id=3660
It's deeply alarming that they'd "disappear" like that. Review Board is
extremely heavily tested with GitHub (we use it every day ourselves, and
monitor a large install with many GitHub users), and haven't come across
this at all yet. Hmmmmm...
We only show "This is an empty file" if it's a newly-created file of 0
bytes. The "new file" state is computed at diff upload time and never
modified, and the number of changes happens when we parse the uploaded file
content and generate a diff view for it.
So I'm seriously leaning toward corruption somewhere.
What type of database are you using?
Are you using any sort of multi-server approach for your web server or
database servers?
Any sort of special work you're doing against the database? Anything with
how you do backups?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.
