Comment #3 on issue 757 by 1153, "Got a packet bigger  
than 'max_allowed_packet' bytes"

I was able to reproduce this issue by submitting a diff that was larger  
than mysql's max_allowed_packet size.

from post-review:

>>> Review request created
>>> Uploading diff, size: 1593200
>>> HTTP POSTing to http://reviews/api/json/reviewrequests/13/diff/new/: {}
Error uploading diff: One or more fields had errors (105)
>>> {u'fields': {u'path': [u'(1153, "Got a packet bigger than  
>>> \'max_allowed_packet\' bytes")']}, u'stat': u'fail',
u'err': {u'msg': u'One or more fields had errors', u'code': 105}}
Your review request still exists, but the diff is not attached.

mysql> show variables like "max_allowed_packet";
| Variable_name      | Value   |
| max_allowed_packet | 1048576 |
1 row in set (0.00 sec)

Note the diff size 1593200 vs the max_allowed_packet default size 1048576 suggests that  
it needs to be a co-
ordinated change on both the client- and server-side.

You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to