Bug #5436
open
Unable To Open Pull Request in 4.11.2
Added by Peter Rebholz almost 7 years ago.
Updated almost 7 years ago.
Description
I upgraded our testing environment to 4.11.2 in order to see if issue #5414 was addressed. I'm unable to successfully open a pull request as there are a few issues in the way:
- When selecting a commit from the Changelog and clicked "open new pull request for selected commit", the source ref field is not set with the commit/bookmark I selected on the Changelog page
- I can't appear to ever select a target revision. It's always blank and clicking on it does not display a drop down.
I noticed an error in the JS console that prints once initially and whenever I change the target repository: TypeError: selectedRef is null. My initial thought was maybe a browser caching issue but after clearing my cache, that doesn't seem to address the issue.
Hi Peter,
I'm unable to reproduce this on mercurial/git repos via branch/fork workflow.
Could you show the cut screen of the changelog references/DAG graph on how the commits look like?
It looks like JS/Static file issues. Could it be your HTTP server cached those somehow?
Hi Marcin,
After poking around a bit more, it seems to happen when the default branch is closed. Things seem to be working for repositories that have the default.
Steps to reproduce:
- Create a repo; make some commits; create a new branch and make some commits; push to RhodeCode
- Fork repository; clone and make some commits; push
- Try to open a pull request from the fork. Everything works.
- In the original repository, close the
default branch and push
- Try to open a pull request from the fork. Source revision is not selected and target box is blank
- In the original repository, re-open the
default branch and push
- Try to open a pull request from the fork. Everything is working again
Hi Peter,
Thanks for the details. It's odd because we tested the "closed" brach case for you, but let us get back to this and i'll let you know.
Ok, confirmed.
We'll fix the case on JS side and make a release for that probably today/tomorrow.
- Status changed from New to Resolved
We just released 4.11.3 version that addresses this case.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by