Re: A weird unicode puzzle after upgrade from 2.0.20 to 2.5.4

2016-05-14 Thread eric via reviewboard 
I re-ran the migration, and before doing anything, set the DEBUG flag to 
True before fetching any diffs.

I can confirm that it fails on *every* diff, not just random ones here and 
there.

Running with DEBUG = False, the warning doesn't throw an exception, but I 
do see an entry in the log:
WARNING:py.warnings:/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py:124:
 
Warning: Invalid utf8 character string: '81FE48'

After I've viewed the diffs of a review request once, the warnings stop 
appearing (consistent with the data being migrated to compressed form.). 
Switching back to DEBUG = True, and I no longer see failures for the review 
request diffs that I looked at while DEBUG = False

Trying a different approach, I ran "rb-site manage __ -- 
condensediffs", and that also generated the same warnings. Here's a sample:

WARNING:py.warnings:/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py:124:
 
Warning: Invalid utf8 character string: 'D76700'

  return self.cursor.execute(query, args)


WARNING:py.warnings:/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py:124:
 
Warning: Invalid utf8 character string: 'A9C813'

  return self.cursor.execute(query, args)


...


This generated 169000+ lines of output, corresponding to 56435 individual 
warning messages out of a total of 76032 diff files condensed.


This gave me an idea.


I ran "rb-site ... condensediffs" before the upgrade, then once again after 
the upgrade.


Problem went away.


Weird. Do you want me to try to find out more, and if so, what?


Eric.



On Friday, May 13, 2016 at 1:49:53 PM UTC-7, Christian Hammond wrote:
>
> Hi Eric,
>
> Hmm, we'll need to look into that. Is there a way you'd be able to send us 
> the diff for that? (I can help you find it.) We will need a copy in order 
> to diagnose this. We can sign an NDA for it.
>
> Christian
>
>
> On Friday, May 13, 2016, eric via reviewboard  > wrote:
>
>> After I migrated my server to 2.5.4, I'm seeing a weird error. I 
>> restarted both memcached and apache2, and then browse to a specific review 
>> request.
>>
>> Then I click on the "Diff" tab. (After I turned on DEBUG = True in the 
>> settings_local.py file) I see this instead of diffs.
>>
>> Traceback (most recent call last):
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/views.py",
>>  
>> line 275, in get
>> response = renderer.render_to_response(request)
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/renderers.py",
>>  
>> line 56, in render_to_response
>> return HttpResponse(self.render_to_string(request))
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/renderers.py",
>>  
>> line 74, in render_to_string
>> large_data=True)
>>   File 
>> "/usr/lib64/python2.7/site-packages/Djblets-0.9.3-py2.7.egg/djblets/cache/backend.py",
>>  
>> line 295, in cache_memoize
>> compress_large_data))
>>   File 
>> "/usr/lib64/python2.7/site-packages/Djblets-0.9.3-py2.7.egg/djblets/cache/backend.py",
>>  
>> line 249, in cache_memoize_iter
>> items = items_or_callable()
>>   File 
>> "/usr/lib64/python2.7/site-packages/Djblets-0.9.3-py2.7.egg/djblets/cache/backend.py",
>>  
>> line 292, in 
>> lambda: [lookup_callable()],
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/renderers.py",
>>  
>> line 73, in 
>> lambda: self.render_to_string_uncached(request),
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/renderers.py",
>>  
>> line 87, in render_to_string_uncached
>> request=request)
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/diffutils.py",
>>  
>> line 429, in populate_diff_chunks
>> chunks = list(generator.get_chunks())
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/chunk_generator.py",
>>  
>> line 756, in get_chunks
>> for chunk in super(DiffChunkGenerator, self).get_chunks(cache_key):
>>   File 
>> "/usr/lib64/python2.7/site-packages/ReviewBoard-2.5.4-py2.7.egg/reviewboard/diffviewer/chunk_generator.py",
>>  
>> line 107, in get_chunks
>> large_data=True)
>>   File 
>> "/usr/lib64/python2.7/site-packages/Djblets-0.9.3-py2.7.egg/djblets/cache/backend.py",
>>  
>> line 295, in cache_memoize
>> compress_large_data))
>>   File 
>> "/usr/lib64/python2.7/site-packages/Djblets-0.9.3-py2.7.egg/djblets/cache/backend.py",
>>  
>> line 249, in cache_memoize_iter
>> items = items_or_callable()
>>   File 
>> "/usr/lib64/python2.7/site-packages/Djblets-0.9.3-py2.7.egg/djblets/cache/backend.py",
>>  
>> line 292, in 
>> lambda: [lookup_callable()],
>>   File 
>>

Re: 504 Gateway Timeout

2016-05-14 Thread Abhishek Choudhary 
This happens when loading the New Review Request page. browsing the already 
created review requests works fine. I am using GIT repository which is 
hosted on a  internal servers.

Steps:
Open dashboard page.
Click on new review request button and the after waiting for about a minute 
the gateway timeout error happens.

On Saturday, May 14, 2016 at 2:21:26 AM UTC+5:30, Christian Hammond wrote:
>
> Hi,
>
> At what point do you see this? When loading the New Review Request page, 
> or browsing commits, or...? Can you walk through every step?
>
> Also, what type of repository, and where is it hosted?
>
> Christian
>
>
> On Friday, May 13, 2016, Abhishek Choudhary  > wrote:
>
>> Hi,
>>
>> I am seeing gateway timeout error with my reviewboard setup whenever i 
>> try to create a new request using 'New Review Request 
>> ' option. Dashboard loads up 
>> pretty quickly and other functionalities are working fine. The problem 
>> occurs with new request only.
>>
>> Server info:
>> Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips 
>> mod_auth_kerb/5.4 mod_wsgi/4.4.11 Python/2.7.11 Server
>>
>> I am not sure where to start looking for the issue. Has anyone seen this 
>> error before?
>>
>> Please help!
>>
>> Thanks,
>> Abhishek
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.