Re: Issue 3966 in reviewboard: Uploading a revision to a CR twice before publishing creates bad partial diffs

Comment #4 on issue 3966 by physicss...@gmail.com: Uploading a revision to a CR twice before publishing creates bad partial diffs https://code.google.com/p/reviewboard/issues/detail?id=3966 Some new info. This appears to be a Chrome- or at least browser-related issue. I cleared Chrome's bro

Re: Issue 3966 in reviewboard: Uploading a revision to a CR twice before publishing creates bad partial diffs

Comment #3 on issue 3966 by physicss...@gmail.com: Uploading a revision to a CR twice before publishing creates bad partial diffs https://code.google.com/p/reviewboard/issues/detail?id=3966 I looked up how to flush memcached and ended up running echo 'flush_all' | nc localhost 11211 This did

Re: Issue 3966 in reviewboard: Uploading a revision to a CR twice before publishing creates bad partial diffs

Updates: Status: NeedInfo Comment #2 on issue 3966 by chip...@gmail.com: Uploading a revision to a CR twice before publishing creates bad partial diffs https://code.google.com/p/reviewboard/issues/detail?id=3966 As a test, what happens if you clear the server cache? Does the problem f

Re: Issue 3966 in reviewboard: Uploading a revision to a CR twice before publishing creates bad partial diffs

Comment #1 on issue 3966 by chip...@gmail.com: Uploading a revision to a CR twice before publishing creates bad partial diffs https://code.google.com/p/reviewboard/issues/detail?id=3966 Thanks for the detailed reproduction steps! We generate the changes between diffs on-the-fly by patching t

Issue 3966 in reviewboard: Uploading a revision to a CR twice before publishing creates bad partial diffs

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3966 by physicss...@gmail.com: Uploading a revision to a CR twice before publishing creates bad partial diffs https://code.google.com/p/reviewboard/issues/detail?id=3966 What version are you running? Reviewboard 2.0.19 an

Re: Issue 3963 in reviewboard: markdown in the field Note to Reviewers gets quoted with backslashes after editing

Comment #4 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 Would you be able to get the API payloads for me at each stage? That'll tell me more. -- You receiv

Re: Issue 3963 in reviewboard: markdown in the field Note to Reviewers gets quoted with backslashes after editing

Comment #3 on 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 Hi, yes, I did publish the review with some notes-for-reviewers set, and then modified t

Re: Issue 3965 in reviewboard: View diff fails for C/C++ files from unified CVS diff

Comment #1 on issue 3965 by boris.bo...@gmail.com: View diff fails for C/C++ files from unified CVS diff https://code.google.com/p/reviewboard/issues/detail?id=3965 Correction Fedora version is 21. -- You received this message because this project is configured to send all issue notificati

Issue 3965 in reviewboard: View diff fails for C/C++ files from unified CVS diff

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3965 by boris.bo...@gmail.com: View diff fails for C/C++ files from unified CVS diff https://code.google.com/p/reviewboard/issues/detail?id=3965 What version are you running? Review Board 2.0.18 What's the URL of the page