Re: Issue 2196 in reviewboard: Aborted drag and drop (drag but no drop) leaves page in disabled state
Comment #4 on issue 2196 by greg.es...@gmail.com: Aborted drag and drop (drag but no drop) leaves page in disabled state http://code.google.com/p/reviewboard/issues/detail?id=2196 Yep, FF 6 is still behaving similarly. Has anybody else been able t replicate the problem? If not, I'll try again with an add-on free FF profile. -- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2257 in reviewboard: RBTools 0.3.3 with Review Board 1.6 RC2 problems with subversion repositories
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2257 by genna...@gmail.com: RBTools 0.3.3 with Review Board 1.6
RC2 problems with subversion repositories
http://code.google.com/p/reviewboard/issues/detail?id=2257
* NOTE: Do not post confidential information in this bug report. *
* If you need immediate support, please contact*
* reviewbo...@googlegroups.com *
What version are you running?
RBTools 0.3.3
Review Board 1.6 RC2
What's the URL of the page containing the problem?
What steps will reproduce the problem?
post-review --repository-url=https://subversion.xxx.xxx/uxxxt/trunk/
--revision-range=917:918 -d
What is the expected output? What do you see instead?
I expect that a review draft will be created.
Instead I have:
...
HTTP GETting https://reviewboard.xxx/api/repositories/13/
HTTP GETting https://reviewboard.xxx/api/repositories/13/info/
repository info: Path: https://subversion.xxx.xxx/uxxxt/, Base
path: /trunk, Supports changesets: False
Attempting to create review request on
https://subversion.xxx.xxx/uxxxt/trunk/ for None
HTTP POSTing to https://reviewboard.xxx/api/review-requests/:
{'repository': 'https://subversion.xxx.xxx/uxxxt/trunk/'}
Got API Error 206 (HTTP code 400): The repository path specified is not
in the list of known repositories
Error data: {u'stat': u'fail', u'repository':
u'https://subversion.xxx.xxx/uxxxt/trunk/', u'err': {u'msg': u'The
repository path specified is not in the list of known repositories',
u'code': 206}}
There was an error creating this review request.
The repository path "https://subversion.xxx.xxx/uxxxt"; is not in the
list of known repositories on the server.
Ask the administrator to add this repository to the Review Board server.
For information on adding repositories, please read
http://www.reviewboard.org/docs/manual/dev/admin/management/repositories/
What operating system are you using? What browser?
Debian
Please provide any additional information below.
RBTool 0.3.2 has no problems
It look like it tries to search for
https://subversion.xxx.xxx/uxxxt/trunk/ instead of
https://subversion.xxx.xxx/uxxxt/
--
You received this message because you are subscribed to the Google Groups
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2256 in reviewboard: post-review should use -c option when calling svn diff with single rev
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2256 by seamus.l...@gmail.com: post-review should use -c option when calling svn diff with single rev http://code.google.com/p/reviewboard/issues/detail?id=2256 What version are you running? 1.6 RC2 What's the URL of the page containing the problem? post-review What steps will reproduce the problem? 1.Point post-review to SVN repo 2.Run post-review with single --revision-range option, e.g. post-review --revision-range=157778 --debug What is the expected output? What do you see instead? Expected debug output: -- RBTools 0.3.3 Home = /home/ svn info diff --version repository info: Path: http:///repo, Base path: //trunk, Supports changesets: False HTTP GETting api/ HTTP GETting http:///reviews/api/info/ Using the new web API svn diff --diff-cmd=diff -c 157778 ^CTraceback (most recent call last): KeyboardInterrupt Actual debug output: RBTools 0.3.3 Home = /home/ svn info diff --version repository info: Path: http:///repo, Base path: //trunk, Supports changesets: False HTTP GETting api/ HTTP GETting http:///reviews/api/info/ Using the new web API svn diff --diff-cmd=diff -r 157778 ^CTraceback (most recent call last): KeyboardInterrupt What operating system are you using? What browser? Ubuntu 9.10 Please provide any additional information below. The documentation states "If you only need to post a single revision, you can type: $ post-review --revision-range=REVISION" However, it uses the -r option with svn diff, which is equivalent to 0:157778, and begins fetching EVERY change made on the current path, up to rev 157778 in this example. It should use the -c option with svn diff. -- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2255 in reviewboard: Issue with the display of a diff in presence of a parent diff
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2255 by balla...@aicas.com: Issue with the display of a diff in presence of a parent diff http://code.google.com/p/reviewboard/issues/detail?id=2255 * NOTE: Do not post confidential information in this bug report. * * If you need immediate support, please contact* * reviewbo...@googlegroups.com * What version are you running? RB 1.5.1 and RB 1.5.2. Issue also present in RB 1.6RC2. What's the URL of the page containing the problem? n/a What steps will reproduce the problem? 1. Create mercurial repository to which RB has access to and a local clone. 2. Create an initial changeset as indicated by this output: plato:sandbox ballarin$ hg up 91c24aa2a306 1 files updated, 0 files merged, 0 files removed, 0 files unresolved plato:sandbox ballarin$ cat mq-test.txt File for investigating an issue of the mercurial reviewboard extension. Posting a request may result in a patch being displayed incorrectly if an ancestor changeset has changed in the meantime. This happens regularly with patch queues. First patch Some space for preventing a conflict between the first and the second patch. Second patch 3. Add a changeset that changes "First patch" to "First patch 1" 4. Add another changeset that changes "Second patch" to "Second patch 2" 5. Push only the initial changeset to the server. The graph is now like this: 91c24aa2a306 (on server) | parent diff cfbda047a23c (local) | diff e86b4f76fcd0 (local) 6. Upload patch e86b4f76fcd0 with cfbda047a23c as parent diff. What is the expected output? What do you see instead? In the attached screen shot, the left column is identified as revision 91c24aa2a306, while it is actually revision cfbda047a23c. (The line "First patch 1" is in cfbda047a23c, while 91c24aa2a306 actually contains "First patch".) This is for mercurial. To exclude problems with the reviewboard extension of mercurial, I uploaded the diffs manually. The observed behaviour is an issue when using mercurial patch queues for working simultaneously on several patches. Then both diff and parent diff can change, and when clicking through the diffs in RB we spotted that the content of the left side changed while this was always identified as the same revision. What operating system are you using? What browser? not relevant Please provide any additional information below. Fixes for this issue are proposed at http://reviews.reviewboard.org/r/2094/. Christian Hammond reported performance issues with the SQLMutation in revision 2 when migrating medium-sized deployments. Revisions 3 and 4 don't use SQLMutations and should not exhibit the problem. Unit tests for this are proposed at http://reviews.reviewboard.org/r/2445/. Attachments: diff.png 194 KB -- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
