I just realized, you're probably being bit by a bug where certain headers
containing Unicode characters would be injected improperly and break some
e-mails. If, for instance, a sender or recipient's name has an accent mark,
you're probably hitting this.
We've fixed this in Git (SHA
Comment #3 on issue 3747 by nano...@gmail.com: Review images is broken
https://code.google.com/p/reviewboard/issues/detail?id=3747
@david,
Is there a chance this issue also affect document (a .docx)?
on our side we've got a 500 error when displaying review request containing
an attachement
Comment #2 on issue 3935 by anthonyh...@gmail.com: Auto populate branch
name when creating new Review Request
https://code.google.com/p/reviewboard/issues/detail?id=3935
Will be working on this as my first easy fix bug.
--
You received this message because this project is configured to send
Comment #4 on issue 3747 by nano...@gmail.com: Review images is broken
https://code.google.com/p/reviewboard/issues/detail?id=3747
I confirm it is the same issue, and David's fix works on any kind of file
attachment. It has solved our issue with .docx
--
You received this message because
Comment #1 on issue 3809 by justin.h...@gmail.com: Broken .kt style in
rb/css/syntax.css
https://code.google.com/p/reviewboard/issues/detail?id=3809
Was able to replicate the problem and looking into it now.
--
You received this message because this project is configured to send all
issue
Hey Christian,
Do you have any other suggestions?
Thanks,
-Zach
On Thursday, September 3, 2015 at 9:46:41 AM UTC-4, Zach wrote:
>
> Our Apache server runs reviewboard as a wsgi daemon process. Its other
> function is to authenticate the user against active directory and then pass
> the
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3962 by phil...@gmail.com: Mercurial repositories not usable on
Windows Reviewboard install when hg is installed with 'pip'
https://code.google.com/p/reviewboard/issues/detail?id=3962
What version are you running?
2.0.19
Since I need to build a ReviewBoard system in a close net environment ,
could anybody tell me if I could do that? Thanks very much
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
Hi,
If you're referring to using the website without any Internet/network
access, like gmail's offline mode, then no. The client requires access to
the API, which often needs to communicate with repositories. We've looked
into building offline access in the past, but it would have massively
Looks like a fine fix. Can you post this on reviews.reviewboard.org?
Thanks!
-David
On Wed, Sep 9, 2015 at 10:33 AM Alexey Neyman
wrote:
> FWIW, converting an iterator to list explicitly seems to help. Changed
> this line:
>
> return
Comment #4 on issue 3954 by alder...@gmail.com: Error 500 to some tickets
https://code.google.com/p/reviewboard/issues/detail?id=3954
I,ve been hitting the same bug with CSV files attachments (pure csv from
php csv writter) as well as doc and docx.
it blocks the whole review when it
Comment #5 on issue 3954 by alder...@gmail.com: Error 500 to some tickets
https://code.google.com/p/reviewboard/issues/detail?id=3954
(FYI 2.0.19 as well, and everything was working before)
--
You received this message because this project is configured to send all
issue notifications to
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3963 by paul.man...@alcatel-lucent.com: markdown in the field
Note to Reviewers gets quoted with backslashes after editing
https://code.google.com/p/reviewboard/issues/detail?id=3963
What version are you running?
2.0.15
FWIW, converting an iterator to list explicitly seems to help. Changed this
line:
return json.dumps(review_ui.serialize_comments(
file_attachment.get_comments()))
to this
return json.dumps(list(review_ui.serialize_comments(
file_attachment.get_comments(
no crash
Comment #2 on issue 3963 by chip...@gmail.com: markdown in the field Note
to Reviewers gets quoted with backslashes after editing
https://code.google.com/p/reviewboard/issues/detail?id=3963
Also, did you publish between steps 1 and 2? If so, I'd be interested in
seeing API data from both
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3964 by zach...@gmail.com: Text Overflow in Search Auto-Complete
for Long Usernames / Long Review Titles
https://code.google.com/p/reviewboard/issues/detail?id=3964
What version are you running?
2.0.18
What's the URL of
This is actually already fixed for 2.0.20, unless I missed something big.
Planning a release in the next few days.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com
On Wed, Sep 9, 2015 at 11:58 AM, David
Updates:
Status: NeedInfo
Labels: Project-ReviewBoard Component-Markdown
Comment #1 on issue 3963 by chip...@gmail.com: markdown in the field Note
to Reviewers gets quoted with backslashes after editing
https://code.google.com/p/reviewboard/issues/detail?id=3963
Interesting.
Comment #6 on issue 3954 by chip...@gmail.com: Error 500 to some tickets
https://code.google.com/p/reviewboard/issues/detail?id=3954
We'll have 2.0.20 out in just a couple days with this fix.
--
You received this message because this project is configured to send all
issue notifications to
19 matches
Mail list logo