Made some progress on this. The problem is not really with the indexing but 
with this:

It is a solution to allow subclass views to have a method called 
get_queryset while also allowing their super class to have the same method 
without causing an method override. It manipulates Python class MRO (method 
resolution order). For some reason in your instance, this code doesn't 
execute correctly and the call to the get_queryset method ends up calling 
itself until Python detects the recursion and stops it via the RunTimeError 
exception. This is the error manifests in document_indexing/ by 
really starts in common/ So in a sense your perception of how it 
behaved liked a caching problem was not far from the real cause.

The solution would be to find the cause and fix 
the PreserveGetQuerysetMixin mixin class (a bit experimental) or remove it 
and do proper method overloading on all classes that use the get_queryset 
method. The mixin class was created to prevent security issues where a view 
would bypass the ACL check from the get_queryset method, on purpose or by 
accident. Will have to choose the lesser of two evils to fix this.

On Monday, August 7, 2017 at 1:48:45 PM UTC-4, David Kimmel wrote:
> Hey Roberto, 
> Since it’s intermittent, it’s pretty tough to write detailed replication 
> steps.  I’ve been keeping an eye on it to see if I could tie a specific 
> action to triggering the problem. 
> Today the indexes broke again and I noticed that it didn’t happen until 
> after I moved a document to the trash.  As soon as I did this, all of my 
> indexes started showing the server error page.  I’m going to continue 
> monitoring and see if any other actions trigger this.  Interestingly 
> enough, I’ve been doing a bunch of updates to the metadata today and did 
> not get the error at all.   
> Are index updates done differently when moving documents to the trash vs 
> updating metadata? 
> This really feels like a caching problem to me, but I honestly don’t know 
> enough about Mayan and Django to know if this is a reasonable assumption. 
> Thanks, 
> -- Dave Kimmel 
> > On Aug 2, 2017, at 13:22, Roberto Rosario <
>> wrote: 
> > 
> > Thanks for reporting this and for the debug information. The first step 
> is to try to make it repeatable to find the cause, things that happen 
> sometimes and sometimes not are very hard to track down. I'll try to write 
> a test to replicate this behavior in development. Thank you. 


You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to