Re: Issue 3018 in reviewboard: post-review can't find source code repository when using TortoiseSVN
Comment #8 on issue 3018 by kova...@gmail.com: post-review can't find source code repository when using TortoiseSVN http://code.google.com/p/reviewboard/issues/detail?id=3018 The cause of issue - TortoiseSVN was installed without command-line tools -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
Issue 3166 in reviewboard: Duplicate user accounts created when authenticating against AD and using allcaps for username
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3166 by fishp...@gmail.com: Duplicate user accounts created when authenticating against AD and using allcaps for username http://code.google.com/p/reviewboard/issues/detail?id=3166 What version are you running? 1.7.11 What's the URL of the page containing the problem? http://reviewboard/account/login/ What steps will reproduce the problem? 1. Connect reviewboard to AD/LADAP 2. Login with an AD user, spelling the username in lowercase 3. Log out 4. Log in with the same user, spelling the username with capitalized letters 5. A duplicate user account is created What is the expected output? What do you see instead? The expectation would be that since AD is not case sensitive for usernames, you end up logged into the same account no matter how you caplitalize your username. What operating system are you using? What browser? Firefox 26, Fedora 18. Please provide any additional information below. You should probably tolower your usernames before checking if they already exist. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 3107 in reviewboard: Negative count of requests
Updates: Status: NeedInfo Comment #4 on issue 3107 by chip...@gmail.com: Negative count of requests http://code.google.com/p/reviewboard/issues/detail?id=3107 I've been trying to reproduce this bug, and just can't. I know there are negative count issues, and I've seen them in the wild, but none of the repro steps seem to work for me. Is there anything in your repro steps you may have left out? Doing exactly those steps doesn't result in a counter issue here. The screenshot you posted is only showing a negative count for stars. Did you star/unstar at any point during this process? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 3018 in reviewboard: post-review can't find source code repository when using TortoiseSVN
Comment #9 on issue 3018 by eyuw...@gmail.com: post-review can't find source code repository when using TortoiseSVN http://code.google.com/p/reviewboard/issues/detail?id=3018 I just found out why, will follow up with you guys. In my case, it was because we didn't use setuptools for installing RBTools, nor did we intend it to be installed by individual users locally. This version (0.5.2) used setuptools to manage scm clients as entry points and later loaded using tools in pkg_resources. A little tweak of entry points works for our infrastructure now. $ ./post-review --version ;./post-review 148092 RBTools 0.5.2 Review request #551754 posted. https://reviewboard.eng.vmware.com/r/551754/ -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 3018 in reviewboard: post-review can't find source code repository when using TortoiseSVN
Comment #10 on issue 3018 by eyuw...@gmail.com: post-review can't find source code repository when using TortoiseSVN http://code.google.com/p/reviewboard/issues/detail?id=3018 I just found out why, will follow up with you guys. In my case, it was because we didn't use setuptools for installing RBTools, nor did we intend it to be installed by individual users locally. This version (0.5.2) used setuptools to manage scm clients as entry points and later loaded using tools in pkg_resources. A little tweak of entry points works for our infrastructure now. $ ./post-review --version ;./post-review 148092 RBTools 0.5.2 Review request #551754 posted. https://.../r/551754/ -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
Issue 3168 in reviewboard: Next/previous hunk keyboard shortcuts not respecting selected file
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3168 by ade...@gmail.com: Next/previous hunk keyboard shortcuts not respecting selected file http://code.google.com/p/reviewboard/issues/detail?id=3168 *** READ THIS BEFORE POSTING! *** *** You must complete this form in its entirety, or your bug report will be rejected. *** *** For customer support, please post to reviewbo...@googlegroups.com *** *** If you have a patch, please submit it to http://reviews.reviewboard.org/ *** *** Do not post confidential information in this bug report! What version are you running? 1.7.16 What's the URL of the page containing the problem? http://our.review-board.url/r/12345/diff/ What steps will reproduce the problem? 1. Click on the link to any of the files except the first. 2. Hit 'n' to go to the first changed hunk. What is the expected output? What do you see instead? I expect to be taken to the first changed hunk in the selected file. Instead, I'm taken to the first changed hunk in the first file in the diff. Put another way, it doesn't look like the next/previous hunk keyboard shortcuts are respecting the file I selected. They definitely used to; we were using version 1.6.3 previously and this worked as I described there. What operating system are you using? What browser? Ubuntu Linux 13.04 with Chromium 31.0.1650.63. Please provide any additional information below. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
