Re: Unable to download attachments that have been uploaded.

2017-10-19 Thread Christian Hammond 
Glad you got it working! Looks like MySQL was missing a core component. Was
it an installation problem?

Christian


On Wed, Oct 18, 2017 at 17:54 Not Saying  wrote:

> I got it working.  THANKS
>
>
> On Tuesday, October 17, 2017 at 10:01:17 AM UTC-7, Not Saying wrote:
>
>> RHEL 7
>> *Review Board*  2.5.15
>>
>> *I click on the download button and it give me a page *This page can’t
>> be displayed
>> The URL is
>> http://localhost/reviewboard/media/uploaded/files/2017/10/16/4654d4a1-10f2-45c5-ab3d-6e9f37b85624__Atsugi_UH_06012017.pdf
>>
>> I see the localhost in the URL where is that defined so I can change it.
>>
>> Thank you.
>>
>> --
> 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.

Re: MariaDB vs MySQL

2017-10-19 Thread David Trowbridge 
Vince,

We haven't directly tested with MariaDB but based on my understanding I
believe it should work just fine.

-David

On Wed, Oct 18, 2017 at 10:19 AM Vince Thyng  wrote:

> Reviewboard currently recommends MySQL 5.6.  MariaDB branches to a 10.x
> numbering with what would have been MariaDB 5.6.  Is anyone using MariaDB
> 10.x in place of MySQL.
>
> Thanks!
>
> Vince
>
> --
> 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.
>

-- 
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.

Re: Index failure after upgrade to ReviewBoard 2.5.16

2017-10-19 Thread 'Rob Backhurst' via reviewboard 
Just to add, the index completed on our test system - thanks all for you 
help with this.
Christian, do you know when this fix will be in a released version?


Also, this may need a separate case so please let me know if you would 
rather I do that...

What is the intended behaviour of the search?
Should the Search API and/or the "quick search" include review requests 
marked as submitted?
If not, when was this changed and why?

Thanks
Rob

On Wednesday, 18 October 2017 14:49:41 UTC+1, Rob Backhurst wrote:
>
> Yep thanks, index looks to be running now.
> Hopefully it will get to the end this time - if so I'll make the same 
> change on our live system.
>
> Cheers
> Rob
>
> On Wednesday, 18 October 2017 14:42:55 UTC+1, Erik Johansson wrote:
>>
>> I'm guessing the if statement should be "if not ..." (i.e. not is 
>> missing).
>>
>> // Erik
>>
>>
>> On Oct 18, 2017 12:44, "'Rob Backhurst' via reviewboard" <
>> revie...@googlegroups.com> wrote:
>>
>> Hi Chris,
>>
>> Ah yes sorry missed that...I have added it in but I get the same error 
>> though.
>>
>>  81 # Check for `__` in the field for looking through the 
>> relation.
>>  82 attrs = self.model_attr.split('__')
>>  83 current_object = obj
>>  84
>>  85 for attr in attrs:
>>  86 hasattr(current_object, attr)
>>  87
>>  88 if hasattr(current_object, attr):
>>  89 raise SearchFieldError("The model '%s' 
>> does not have a model_attr '%s'." % (repr(current_object), attr))
>>  90
>>  91 current_object = getattr(current_object, attr, 
>> None)
>>  92
>>  93 if current_object is None:
>>  94 if self.has_default():
>>  95 current_object = self._default
>>  96 # Fall out of the loop, given any further 
>> attempts at
>>
>>
>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 89, in 
>> prepare
>> raise SearchFieldError("The model '%s' does not have a model_attr 
>> '%s'." % (repr(current_object), attr))
>> haystack.exceptions.SearchFieldError: The model '' does not 
>> have a model_attr 'username'.
>>
>>
>> Thanks
>> Rob
>>
>>
>>
>> On Wednesday, 18 October 2017 10:02:54 UTC+1, Christian Hammond wrote:
>>
>>> Hi Rob,
>>>
>>> That doesn't include the code I mentioned in my previous e-mail. Note 
>>> the standalone 'hasattr' call on the line preceding the if statement. The 
>>> workaround is to call that in a standalone way to prime a cache and avoid 
>>> the error.
>>>
>>> Christian
>>>
>>> On Tue, Oct 17, 2017 at 1:17 AM, 'Rob Backhurst' via reviewboard <
>>> revie...@googlegroups.com> wrote:
>>>
  77 # Give priority to a template.
  78 if self.use_template:
  79 return self.prepare_template(obj)
  80 elif self.model_attr is not None:
  81 # Check for `__` in the field for looking through 
 the relation.
  82 attrs = self.model_attr.split('__')
  83 current_object = obj
  84
  85 for attr in attrs:
  86 if hasattr(current_object, attr):
  87 raise SearchFieldError("The model '%s' 
 does not have a model_attr '%s'." % (repr(current_object), attr))
  88
  89 current_object = getattr(current_object, attr, 
 None)
  90
  91 if current_object is None:
  92 if self.has_default():
  93 current_object = self._default
  94 # Fall out of the loop, given any 
 further attempts at
  95 # accesses will fail misreably.


 Thanks
 Rob

 On Tuesday, 17 October 2017 06:28:49 UTC+1, Christian Hammond wrote:
>
> Can you show me all the code within about 5 lines of your modification?
>
> Christian
>
>
> On Mon, Oct 16, 2017 at 18:01 'Rob Backhurst' via reviewboard <
> revie...@googlegroups.com> wrote:
>
>> Hi Christian,
>>
>> It crashes straight away with this error...
>>
>> Removing all documents from your index because you said so.
>> All documents removed.
>> Indexing 558 users
>> ERROR:root:Error updating auth using default
>> Traceback (most recent call last):
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>  
>> line 188, in handle_label
>> self.update_backend(label, using)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>  
>> line 233, in update_backend
>> do_update(backend, index, qs, start, end, total, 
>> verbosity=self.verbosity,