3785: Publish changes fails

jona****@nextcomme********** (Google Code) (Is this you? Claim this profile.)
March 13, 2015
Hi there,

So here is the situation:

My usual workflow: I file a new code review, I fill all the test things, fix details in the summary and description, I fill the branch and the group, then click publish.

Recently it's a bit slow and I can see that just before submitting, the whole form is being emptied and I get the message:
"There must be at least one reviewer before this review request can be published."

Then the branch and the group (which I filled before) are empty.

My workaround: I put one specific person in the People box and for some reason it works.

But now I want to update my review with a new diff. I see the message telling me "This review request is a draft. Be sure to publish when finished." so I click publish, and same things happens. The whole form is emptied, and I get the alert message:
"There must be at least one reviewer before this review request can be published."

I use Chrome 39.0.2171.95 (64-bit) on OSx 10.9.5
it works perfectly fine with Safari 7.1.2 (9537.85.11.5) on the same machine
david
#1 david
What version of Review Board?
  • +NeedInfo
#2 jona****@nextcomme********** (Google Code) (Is this you? Claim this profile.)
I'm using the hosted version, I don't know which version is that. I'd assume the latest?
chipx86
#3 chipx86
Hi Jonathan,

Sorry for the confusion, and thanks for the report. You can also reach out to us at support@beanbaginc.com.

Are you still seeing this for any review requests? If so, can you provide the page source to us at that e-mail address? We're trying to determine whether this is a stale version of our JavaScript being used, or something else.
david
#4 david
This has been resolved.
  • -NeedInfo
    +Fixed
grossag
#5 grossag
I'm seeing this at VMware too; I cleared Chrome's cache but it only provides a temporary reprieve from the issue.  Do you have a version number where this is fixed so I can ask us the company to ugprade upgrade?
chipx86
#6 chipx86
Yeah, 2.0.14 fixes it, though we recommend 2.0.15 for further improvements. There's enough moving parts involved for the fixes that an upgrade, rather than backported patches, will be needed.