Re: Comment on GettingStarted in reviewboard
Comment by messaget...@gmail.com: Hi Please add me to view the blog. messagetoleg...@gmail.com thanks Vinod Kumar For more information: http://code.google.com/p/reviewboard/wiki/GettingStarted -- 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 2239 in reviewboard: Adding comment to review does not work with Chrome 14.0.835.94
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2239 by shankar@gmail.com: Adding comment to review does not work with Chrome 14.0.835.94 http://code.google.com/p/reviewboard/issues/detail?id=2239 * 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? 1.5.5 What's the URL of the page containing the problem? The review page (/r/reviewnum) What steps will reproduce the problem? 1. Visit a review request that has some reviews already posted. 2. Click on Add comment after one of the reviews 3. What is the expected output? What do you see instead? I expect a text box to open up, where I can add a comment, and click on Save. Instead, what happens is that a blank comment is added (as if I had hit save on an empty textbox), and no Publish button (or any other button) shows up. What operating system are you using? What browser? Chrome 14.0.835.94, on both MacOS 10.6.8 and Windows 2008 R2. Please provide any additional information below. This is a problem caused by a recent update to Chrome. Used to work fine in the 13.* series and before. -- 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 2240 in reviewboard: Error while running the commad - post-review multitest.txt
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2240 by asa.amgo...@gmail.com: Error while running the commad - post-review multitest.txt http://code.google.com/p/reviewboard/issues/detail?id=2240 * 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? 1.6 RC2 What's the URL of the page containing the problem? While creating the review request, not taking the diff file which is created from cleartool diff -pre. Also facing issue in command line from linux What steps will reproduce the problem? 1.We have installed the ReviewBoard as mentioned in the install procedure 2.Created dynamic view running the command being in the /view/view-name/vobs/vob-name path 3. Repository created for /view/view-name/vobs/vob-name What is the expected output? What do you see instead? Need to create a review request with the diff information Failed to execute command: ['cleartool', 'desc', '-pre', '/vobs/vob-name/multitest.txt'] ['cleartool: Error: Unable to access /vobs/vob-name/multitest.txt: No such file or directory.\n'] What operating system are you using? What browser? Linux 2.6.32-71.el6.x86_64 #1 SMP Wed Sep 1 01:33:01 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux Firefox 5.0 Please provide any additional information below. We are planning to configure CC with Review Board, now we can use without CC integration. So please help us to configure CC and use the RB for CC -- 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.
Re: Issue 2240 in reviewboard: Error while running the commad - post-review multitest.txt
Updates: Status: NeedInfo Comment #1 on issue 2240 by chip...@gmail.com: Error while running the commad - post-review multitest.txt http://code.google.com/p/reviewboard/issues/detail?id=2240 What version of RBTools are you using? -- 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.
Re: Issue 2186 in reviewboard: Upgrading site on 1.6 RC2 gives evolution errors
Comment #9 on issue 2186 by chris.a@gmail.com: Upgrading site on 1.6 RC2 gives evolution errors http://code.google.com/p/reviewboard/issues/detail?id=2186 Attached are the dumps of those tables. It's a best guess, but I've probably used every version of 1.5 since beta 2, and have used 1.6 RC2 on this install. Attachments: django_project_version.sql 169 KB django_evolution.sql 2.9 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.
Issue 2241 in reviewboard: failed diffs are stored in memcached and not being updated after fixing the actual problem
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2241 by sergey.s...@googlemail.com: failed diffs are stored in memcached and not being updated after fixing the actual problem http://code.google.com/p/reviewboard/issues/detail?id=2241 * 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? 1.5.5 What's the URL of the page containing the problem? diff page, e.g. http://reviewboard-server/r/4446/diff/#index_header What steps will reproduce the problem? 0. Use reviewboard+memcached 1. Use mercurial repository 2. Create 2 commits, don't push 3. Created diff for 2nd commit, submit it to reviewboard 4. Try to view diff -- you will get error as reviewboard is not aware about not-pushed parent commit 5. Make push 6. Reload diff in reviewboard. You will expect it to work now, as all required data is in repository, but you will get the same error. 7. restart memcached 8. no you can see correct diff What is the expected output? What do you see instead? see steps What operating system are you using? What browser? reviewboard in installed on Ubuntu 9.04 latest memcached version Please provide any additional information below. -- 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 2242 in reviewboard: failed diffs are stored in memcached and not being updated after fixing the actual problem
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2242 by sergey.s...@googlemail.com: failed diffs are stored in memcached and not being updated after fixing the actual problem http://code.google.com/p/reviewboard/issues/detail?id=2242 * 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? 1.5.5 What's the URL of the page containing the problem? diff page, e.g. http://reviewboard-server/r/4446/diff/#index_header What steps will reproduce the problem? 0. Use reviewboard+memcached 1. Use mercurial repository 2. Create 2 commits, don't push 3. Created diff for 2nd commit, submit it to reviewboard 4. Try to view diff -- you will get error as reviewboard is not aware about not-pushed parent commit 5. Make push 6. Reload diff in reviewboard. You will expect it to work now, as all required data is in repository, but you will get the same error. 7. restart memcached 8. no you can see correct diff What is the expected output? What do you see instead? see steps What operating system are you using? What browser? reviewboard in installed on Ubuntu 9.04 latest memcached version Please provide any additional information below. -- 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.
Re: Issue 2186 in reviewboard: Upgrading site on 1.6 RC2 gives evolution errors
Comment #10 on issue 2186 by chip...@gmail.com: Upgrading site on 1.6 RC2 gives evolution errors http://code.google.com/p/reviewboard/issues/detail?id=2186 Thanks. I suspect if you upgrade to the latest Django-Evolution and the latest RB 1.6 nightly, the problem will go away. Would you mind trying that? -- 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.
Re: Issue 2186 in reviewboard: Upgrading site on 1.6 RC2 gives evolution errors
Comment #11 on issue 2186 by chris.a@gmail.com: Upgrading site on 1.6 RC2 gives evolution errors http://code.google.com/p/reviewboard/issues/detail?id=2186 Attached are the dumps of those tables. It's a best guess, but I've probably used every version of 1.5 since beta 2, and have used 1.6 RC2 on this install. Attachments: django_project_version.sql 169 KB django_evolution.sql 2.9 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.
Issue 2243 in reviewboard: New RBTools 0.3.3 doesn't work with RB 1.0.1
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2243 by zhaokun7...@gmail.com: New RBTools 0.3.3 doesn't work
with RB 1.0.1
http://code.google.com/p/reviewboard/issues/detail?id=2243
* 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?
I just installed RBTools 0.3.3 in my MacBook Pro, and the RB server version
is 1.0.1.
I am trying to post-review but failed with the following error.
Traceback (most recent call last):
File /usr/local/bin/post-review, line 8, in module
load_entry_point('RBTools==0.3.3', 'console_scripts', 'post-review')()
File build/bdist.linux-x86_64/egg/rbtools/postreview.py, line 3988, in
main
AttributeError: 'ReviewBoardServer' object has no attribute 'rb_version'
Does this mean RBTools 0.3.3 doesn't support the old RB server?
--
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 2244 in reviewboard: API Request: Ability to determine if a review request is marked as ship it without having to iterate through reviews
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2244 by lesleyli...@gmail.com: API Request: Ability to determine if a review request is marked as ship it without having to iterate through reviews http://code.google.com/p/reviewboard/issues/detail?id=2244 *NOTE: If you have a patch, please submit it to http://reviews.reviewboard.org/ What version are you running? 1.5.2 What's the URL of the page this enhancement relates to, if any? http://www.reviewboard.org/docs/manual/1.5/webapi/2.0/resources/review-request/ Describe the enhancement and the motivation for it. I'm working on writing an app that displays a list of pending reviews that have not already marked as ship it. Currently, in order to find out if a review is marked as ship it, you need to make another json request for each review in the review request's list, and check if the review has marked the request as ship it. On the main dashboard, one can display an additional column that says how many ship it comments a request has. API like that would be exactly what I'm looking for. What operating system are you using? What browser? OS X 10.7 Please provide any additional information below. -- 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 2245 in reviewboard: API Request: Ability to determine the base directory a patch was created from
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2245 by lesleyli...@gmail.com: API Request: Ability to determine the base directory a patch was created from http://code.google.com/p/reviewboard/issues/detail?id=2245 *NOTE: If you have a patch, please submit it to http://reviews.reviewboard.org/ What version are you running? 1.5.2 What's the URL of the page this enhancement relates to, if any? http://www.reviewboard.org/docs/manual/1.5/webapi/2.0/resources/diff/ Describe the enhancement and the motivation for it. I'm working on an app that downloads diffs from rb and applies them to my local sandbox. Currently, there's no way to tell what directory the patch was created from without looking at the website. The diff API tells us the repository, but it would be extremely useful if it told you the base directory the diff was created from as well What operating system are you using? What browser? Please provide any additional information below. -- 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.
Re: Issue 2243 in reviewboard: New RBTools 0.3.3 doesn't work with RB 1.0.1
Updates: Status: Confirmed Labels: -Priority-Medium Priority-Low Component-RBTools Comment #1 on issue 2243 by chip...@gmail.com: New RBTools 0.3.3 doesn't work with RB 1.0.1 http://code.google.com/p/reviewboard/issues/detail?id=2243 1.0.1 is a few years old at this point. In general, we're not supporting 1.0.x. However, there's probably an easy fix for this. For now, downgrade your RBTools. Future versions in the 0.4.x through 1.0 series won't support 1.0.x at all. -- 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.
