I just found: "cloning per https is blocked from the internet, if you want to clone from internet you need to use ssh" That seems like the real problem... sooo... How can I persuade Reviewboard to communicate with GitLab over SSH?
Dne úterý 16. června 2020 15:05:43 UTC+2 kort...@email.cz napsal(a): > > Yes, the RBTools seems completely different problem (and we might solve it > yet, we found what we did wrong, need some more testing). We will open > different thread if needed. > > The branch limit is also not an issue anymore, we changed the structure, > so now we can reach the branches we need, and as you said - will be solved > in next release. > > But the problem with the access is still an isssue. I have tried with > several users, included the owner of the repository. Every one has the same > issue. > Every user I tested is able to make a clone of the repository, so they > definetly should have access. > > If I check in GitLab, it does not even register usage of the API token. > > One of my colleagues said he had also problem with access to the > repository from another tool (Jenkins). He found out the problem is with > the HTTPS access. He managed to successfully access the repository with > SSH. This is why I wanted to try the general Git repository entry, because > there is possibilitiy to set an SSH entry there. > > I am also communicating with our GitLab support, but they are not much > helpfull yet... I have some new name to contact, so hopefully he will have > some insight. > > > Thank you for still keeping this thread active, I already spent too much > time on this and the management is starting to have questions, so if I do > not solve it soon, I will have to go for another review tool... > > > > Dne pondělí 8. června 2020 0:03:44 UTC+2 Christian Hammond napsal(a): >> >> There’s two things in this thread that I think are getting jumbled >> together. There’s the RBTools issue, and the GitLab configuration. They’re >> independent, and I think it’s best to focus on one per thread. >> >> For GitLab, it sounds like there’s two issues: >> >> 1) The branch limit. This will be fixed in the next release. That release >> is delayed as my primary computer is currently awaiting its position in a >> queue at Apple for repairs, and I’m in lockdown, making this a bit more >> difficult to deal with than normal... >> >> 2) Access control issues with that repository, which seems to be the more >> urgent issue. >> >> You mentioned the 1.5 docs, and tried solutions from it, but much has >> changed since 1.5. Nothing from there will be helpful, and there’s no way >> for a non-GitLab Git repository entry to talk to GitLab. You won’t want to >> go down that path any further. It’s a hard requirement to use the GitLab >> hosting type to talk to a GitLab repository. >> >> It does still seem to me to be an issue with the accessing user not >> having permissions to access commit info on the repository in question. >> What can you tell me about that user? >> >> Christian >> >> >> >> On Thu, May 28, 2020 at 09:00 kort...@email.cz <kort...@email.cz> wrote: >> >>> Hi Christian, >>> >>> Unfortunately I am still struggling. >>> >>> The gitlab support directed me to check this: >>> https://www.reviewboard.org/docs/manual/1.5/admin/management/repositories/#determining-repository-information >>> >>> This sounded like exactly my problem, for I see the branches, but cannot >>> access a single file. I then realized that is nonsense, because if that >>> would be the problem, then it wouldn't work even for the public repository >>> (I tested it myself, and really when I switch a repository to public, it >>> magically starts to work). >>> >>> But it gave me the idea to try to add the repository as "custom >>> repository" and try to fill in the "Raw file URL mask" - I tried it and >>> encountered another error :-( >>> >>> Environment can only contain strings >>> >>> I found by google, that this was a discussed error at around 2015, but >>> no solution was presented. Is it some bug that returned? Can I do something >>> with it? >>> >>> I tried to explore some more in the Gitlab and Reviewboard settings - >>> tried something called deploy token and deploy keys, but nothing seems to >>> work. >>> >>> Also I found I can add applications to my Gitlab account, but I need >>> something called "Redirect URI" but I have no idea where to get it for >>> Reviewboard... I tried to put there my reviewboard server address, but that >>> don't work either. >>> >>> What I found out is that when I try to create the review, the Gitlab do >>> not even register any movement on my account. So I really believe the >>> problem is somewhere in the API token and logging and recognizing the user. >>> Couldn't a problem be, that we use two-factor authentication and a Siemens >>> entitlement for logging into the Gitlab repository? The API token should be >>> able to pierce that though, shouldn't it? >>> >>> I am getting frustrated by this to be honest, for it seems we will have >>> to try out some another tool, which is exactly what I wanted to avoid, for >>> we already approved that Reviewboard is suitable for our SIL needs. >>> >>> About the RBTools problem - Martin had some computer breakdown and >>> cannot continue with the experiments at the moment. He will continue as >>> soon as he is able. >>> >>> Thanks for any further help, I am currently running out of ideas. >>> >>> Dne pátek 22. května 2020 23:00:15 UTC+2 Christian Hammond napsal(a): >>>> >>>> Hi Martin, >>>> >>>> The error is coming from Git, it seems. Can you run this command from >>>> that directory and see what it says: >>>> >>>> git symbolic-ref -q HEAD >>>> >>>> Christian >>>> >>>> >>>> On Fri, May 22, 2020 at 08:51 Martin Růžek <ruze...@gmail.com> wrote: >>>> >>> Hi, >>>>> >>>>> I'm that person trying to use it on real repository. >>>>> I hit this error even during setup-repo command. I passed --debug >>>>> parameter and output looks like this: >>>>> >>>>> *D:\git_repository>rbt setup-repo --debug* >>>>> *>>> RBTools 1.0.3* >>>>> *>>> Python 2.7.17 (v2.7.17:c2f86d86e6, Oct 19 2019, 20:49:36) [MSC >>>>> v.1500 32 bit (Intel)]* >>>>> *>>> Running on Windows-10-10.0.17134* >>>>> *>>> Home = C:\Users\z003fbrn\AppData\Roaming* >>>>> *>>> Current directory = d:\Ruzek\LEIA\Emitter\sitrans-tdl-emitter* >>>>> *>>> Command line: rbt setup-repo --debug* >>>>> *Enter the Review Board server URL: >>>>> https://czprga99033srv.ad001.siemens.net:444/ >>>>> <https://czprga99033srv.ad001.siemens.net:444/>* >>>>> *>>> Running: tf vc help* >>>>> *>>> Checking for a Subversion repository...* >>>>> *>>> Unable to execute "svn help": skipping SVN* >>>>> *>>> Checking for a Git repository...* >>>>> *>>> Running: git rev-parse --git-dir* >>>>> *>>> Running: git config core.bare* >>>>> *>>> Running: git rev-parse --show-toplevel* >>>>> *>>> Running: git symbolic-ref -q HEAD* >>>>> *Traceback (most recent call last):* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\bin\..\Python27\Scripts\rbt-script.py", line 11, in >>>>> <module>* >>>>> * load_entry_point('RBTools==1.0.3', 'console_scripts', 'rbt')()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\main.py", >>>>> >>>>> line 120, in main* >>>>> * command.run_from_argv([RB_MAIN, command_name] + args)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\__init__.py", >>>>> >>>>> line 725, in run_from_argv* >>>>> * exit_code = self.main(*args) or 0* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\setup_repo.py", >>>>> >>>>> line 105, in main* >>>>> * repository_info, tool = self.initialize_scm_tool()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\__init__.py", >>>>> >>>>> line 754, in initialize_scm_tool* >>>>> * client_name=client_name)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\clients\__init__.py", >>>>> >>>>> line 803, in scan_usable_client* >>>>> * repository_info = tool.get_repository_info()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\clients\git.py", >>>>> >>>>> line 284, in get_repository_info* >>>>> * ignore_errors=True).strip()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\clients\git.py", >>>>> >>>>> line 1261, in _execute* >>>>> * return execute(cmdline, cwd=self._git_toplevel, *args, **kwargs)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\utils\process.py", >>>>> >>>>> line 155, in execute* >>>>> * **popen_encoding_args)* >>>>> * File "C:\Program Files (x86)\RBTools\Python27\lib\subprocess.py", >>>>> line 394, in __init__* >>>>> * errread, errwrite)* >>>>> * File "C:\Program Files (x86)\RBTools\Python27\lib\subprocess.py", >>>>> line 644, in _execute_child* >>>>> * startupinfo)* >>>>> *WindowsError: [Error 267] The directory name is invalid* >>>>> >>>>> If I try post command, report looks like this: >>>>> >>>>> *d:\git_repository>rbt post --debug* >>>>> *>>> RBTools 1.0.3* >>>>> *>>> Python 2.7.17 (v2.7.17:c2f86d86e6, Oct 19 2019, 20:49:36) [MSC >>>>> v.1500 32 bit (Intel)]* >>>>> *>>> Running on Windows-10-10.0.17134* >>>>> *>>> Home = C:\Users\z003fbrn\AppData\Roaming* >>>>> *>>> Current directory = d:\Ruzek\LEIA\Emitter\sitrans-tdl-emitter* >>>>> *>>> Command line: rbt post --debug* >>>>> *>>> Running: tf vc help* >>>>> *>>> Checking for a Subversion repository...* >>>>> *>>> Unable to execute "svn help": skipping SVN* >>>>> *>>> Checking for a Git repository...* >>>>> *>>> Running: git rev-parse --git-dir* >>>>> *>>> Running: git config core.bare* >>>>> *>>> Running: git rev-parse --show-toplevel* >>>>> *>>> Running: git symbolic-ref -q HEAD* >>>>> *Traceback (most recent call last):* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\bin\..\Python27\Scripts\rbt-script.py", line 11, in >>>>> <module>* >>>>> * load_entry_point('RBTools==1.0.3', 'console_scripts', 'rbt')()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\main.py", >>>>> >>>>> line 120, in main* >>>>> * command.run_from_argv([RB_MAIN, command_name] + args)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\__init__.py", >>>>> >>>>> line 725, in run_from_argv* >>>>> * exit_code = self.main(*args) or 0* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\post.py", >>>>> >>>>> line 756, in main* >>>>> * client_name=self.options.repository_type)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\commands\__init__.py", >>>>> >>>>> line 754, in initialize_scm_tool* >>>>> * client_name=client_name)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\clients\__init__.py", >>>>> >>>>> line 803, in scan_usable_client* >>>>> * repository_info = tool.get_repository_info()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\clients\git.py", >>>>> >>>>> line 284, in get_repository_info* >>>>> * ignore_errors=True).strip()* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\clients\git.py", >>>>> >>>>> line 1261, in _execute* >>>>> * return execute(cmdline, cwd=self._git_toplevel, *args, **kwargs)* >>>>> * File "C:\Program Files >>>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-1.0.3-py2.7.egg\rbtools\utils\process.py", >>>>> >>>>> line 155, in execute* >>>>> * **popen_encoding_args)* >>>>> * File "C:\Program Files (x86)\RBTools\Python27\lib\subprocess.py", >>>>> line 394, in __init__* >>>>> * errread, errwrite)* >>>>> * File "C:\Program Files (x86)\RBTools\Python27\lib\subprocess.py", >>>>> line 644, in _execute_child* >>>>> * startupinfo)* >>>>> *WindowsError: [Error 267] The directory name is invalid* >>>>> >>>>> Martin >>>>> >>>>> Dne pátek 22. května 2020 11:58:58 UTC+2 Christian Hammond napsal(a): >>>>>> >>>>>> That error doesn’t make much sense to me. It sounds like it’s being >>>>>> run from a directory that was then deleted, or there’s some special >>>>>> characters or something that something is having trouble with. >>>>>> >>>>>> I’d like to see more about how you’re using RBTools. Can you go into >>>>>> detail on your setup, how you’re invoking it? >>>>>> >>>>>> I’d also like to see the debug output from the invocation that leads >>>>>> to that error. You can pass --debug as the first parameter to `rbt post`. >>>>>> >>>>>> Christian >>>>>> >>>>>> >>>>>> On Tue, May 19, 2020 at 05:46 kort...@email.cz <kort...@email.cz> >>>>>> wrote: >>>>>> >>>>> Hi Christian, >>>>>>> >>>>>>> Thanks, I have contacted our GitLab support and hopefully it will >>>>>>> have a good ending. >>>>>>> >>>>>>> The colleague testing the RBTools was using this guide >>>>>>> https://www.reviewboard.org/docs/rbtools/1.0/workflows/git/#rbtools-workflow-git >>>>>>> But ended with >>>>>>> CRITICAL: [Error 267] The directory name is invalid >>>>>>> when tried using rbt post >>>>>>> >>>>>>> I tried to google around for it, but got nothing usefull... >>>>>>> >>>>>>> >>>>>>> Dne úterý 19. května 2020 2:21:05 UTC+2 Christian Hammond napsal(a): >>>>>>>> >>>>>>>> It doesn't ring any bells. It does sound like a >>>>>>>> credential/repository access issue, though. I suspect *something* is >>>>>>>> preventing that user from accessing changes on that repository in >>>>>>>> GitLab's >>>>>>>> settings. I know other companies are using private repositories on >>>>>>>> GitLab >>>>>>>> with Review Board without issue. >>>>>>>> >>>>>>>> What's the problem you're hitting with RBTools? >>>>>>>> >>>>>>>> Christian >>>>>>>> >>>>>>>> On Mon, May 18, 2020 at 9:04 AM kort...@email.cz <kort...@email.cz> >>>>>>>> wrote: >>>>>>>> >>>>>>> Update: >>>>>>>>> >>>>>>>>> When we tested it with a "public" repository on our gitlab server, >>>>>>>>> it works. But our repositories needs to be private. >>>>>>>>> >>>>>>>>> So it seems the problem is somewhere in the recognition of the >>>>>>>>> reviewboard as a valid user, even though I filled in all the tokens >>>>>>>>> and >>>>>>>>> keys and user credentials... >>>>>>>>> >>>>>>>>> Rings any bells? >>>>>>>>> >>>>>>>>> Dne pondělí 18. května 2020 16:47:21 UTC+2 kort...@email.cz >>>>>>>>> napsal(a): >>>>>>>>>> >>>>>>>>>> Hi Christian, >>>>>>>>>> >>>>>>>>>> Thanks for the ideas, my admin managed to update reviewboard to >>>>>>>>>> 3.0.17, but no luck. >>>>>>>>>> I found out I am missing the SSH settings, so I created a new one >>>>>>>>>> and added the public part to our gitlab repository, but that was not >>>>>>>>>> it >>>>>>>>>> either... >>>>>>>>>> >>>>>>>>>> I am running out of ideas... is there some information I can give >>>>>>>>>> you so you can help me? >>>>>>>>>> >>>>>>>>>> For some reason we were not able to make the RBTools run either. >>>>>>>>>> >>>>>>>>>> I would hate to have to look for another tool:( >>>>>>>>>> >>>>>>>>>> Dne pondělí 18. května 2020 5:19:48 UTC+2 Christian Hammond >>>>>>>>>> napsal(a): >>>>>>>>>>> >>>>>>>>>>> Hi Jirka, >>>>>>>>>>> >>>>>>>>>>> We've fixed the pagination issue and will have the fix in 3.0.18. >>>>>>>>>>> >>>>>>>>>>> I don't know what's going on in that backtrace, but 3.0.12 is >>>>>>>>>>> pretty old now, so it may have been a bug in an older release. Or >>>>>>>>>>> some >>>>>>>>>>> change in their API we're not aware of, or something else getting >>>>>>>>>>> in the >>>>>>>>>>> way of access. I unfortunately don't have enough information to go >>>>>>>>>>> off of >>>>>>>>>>> from the backtrace. Just that the API for fetching a change is >>>>>>>>>>> returning a >>>>>>>>>>> HTTP 404. >>>>>>>>>>> >>>>>>>>>>> I'd try upgrading and also make sure there aren't any >>>>>>>>>>> restrictions on the user configured in Review Board to authenticate >>>>>>>>>>> with >>>>>>>>>>> GitLab. >>>>>>>>>>> >>>>>>>>>>> Christian >>>>>>>>>>> >>>>>>>>>>> On Fri, May 15, 2020 at 6:30 AM kort...@email.cz < >>>>>>>>>>> kort...@email.cz> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi again, >>>>>>>>>>>> >>>>>>>>>>>> There is another problem... I tried to create a review request >>>>>>>>>>>> from the branches and commits I see and I get >>>>>>>>>>>> "HTTP 500 INTERNAL SERVER ERROR" >>>>>>>>>>>> >>>>>>>>>>>> What is wrong? Any idea? Isn't the problem, that our >>>>>>>>>>>> reviewboard is running on https and port number 444? >>>>>>>>>>>> >>>>>>>>>>>> Log for this error: >>>>>>>>>>>> ERROR >>>>>>>>>>>> >>>>>>>>>>>> - root - Unable to update new review request from commit ID >>>>>>>>>>>> 6a60ac36244fb185817055e6e9c404106b103260 on repository ID=2: HTTP >>>>>>>>>>>> Error 404: Not Found >>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\reviews\managers.py", >>>>>>>>>>>> line 165, in create >>>>>>>>>>>> draft.update_from_commit_id(commit_id) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\reviews\models\review_request_draft.py", >>>>>>>>>>>> line 419, in update_from_commit_id >>>>>>>>>>>> return self.update_from_committed_change(commit_id) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\reviews\models\review_request_draft.py", >>>>>>>>>>>> line 492, in update_from_committed_change >>>>>>>>>>>> commit = self.repository.get_change(commit_id) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\scmtools\models.py", >>>>>>>>>>>> line 509, in get_change >>>>>>>>>>>> return hosting_service.get_change(self, revision) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\hostingsvcs\gitlab.py", >>>>>>>>>>>> line 641, in get_change >>>>>>>>>>>> headers={'Accept': 'text/plain'}) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\hostingsvcs\service.py", >>>>>>>>>>>> line 188, in http_get >>>>>>>>>>>> return self.http_request(url, headers=headers, method='GET', >>>>>>>>>>>> **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\hostingsvcs\service.py", >>>>>>>>>>>> line 319, in http_request >>>>>>>>>>>> response = urlopen(request, context=context) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 154, in urlopen >>>>>>>>>>>> return opener.open(url, data, timeout) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 435, in open >>>>>>>>>>>> response = meth(req, response) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 548, in http_response >>>>>>>>>>>> 'http', request, response, code, msg, hdrs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 467, in error >>>>>>>>>>>> result = self._call_chain(*args) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 407, in _call_chain >>>>>>>>>>>> result = func(*args) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 654, in http_error_302 >>>>>>>>>>>> return self.parent.open(new, timeout=req.timeout) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 435, in open >>>>>>>>>>>> response = meth(req, response) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 548, in http_response >>>>>>>>>>>> 'http', request, response, code, msg, hdrs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 473, in error >>>>>>>>>>>> return self._call_chain(*args) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 407, in _call_chain >>>>>>>>>>>> result = func(*args) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\urllib2.py", >>>>>>>>>>>> line 556, in http_error_default >>>>>>>>>>>> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) >>>>>>>>>>>> HTTPError: HTTP Error 404: Not Found >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> and >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ERROR >>>>>>>>>>>> >>>>>>>>>>>> None - jiri.kortanek - /api/review-requests/ - >>>>>>>>>>>> djblets.log.middleware - Exception thrown for user jiri.kortanek >>>>>>>>>>>> at https://myserver.ad001.mycompany.net:444/api/review-requests/ >>>>>>>>>>>> >>>>>>>>>>>> HTTP Error 404: Not Found >>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\django\django\core\handlers\base.py", >>>>>>>>>>>> line 112, in get_response >>>>>>>>>>>> response = wrapped_callback(request, *callback_args, >>>>>>>>>>>> **callback_kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\django\django\views\decorators\cache.py", >>>>>>>>>>>> line 52, in _wrapped_view_func >>>>>>>>>>>> response = view_func(request, *args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\django\django\views\decorators\vary.py", >>>>>>>>>>>> line 19, in inner_func >>>>>>>>>>>> response = func(*args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\site-packages\djblets\webapi\resources\base.py", >>>>>>>>>>>> line 244, in __call__ >>>>>>>>>>>> request, method, view, api_format=api_format, *args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\webapi\base.py", >>>>>>>>>>>> line 338, in call_method_view >>>>>>>>>>>> request, method, view, *args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\site-packages\djblets\webapi\resources\mixins\api_tokens.py", >>>>>>>>>>>> line 66, in call_method_view >>>>>>>>>>>> request, method, view, *args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\site-packages\djblets\webapi\resources\mixins\oauth2_tokens.py", >>>>>>>>>>>> line 102, in call_method_view >>>>>>>>>>>> request, method, view, *args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\site-packages\djblets\webapi\resources\base.py", >>>>>>>>>>>> line 369, in call_method_view >>>>>>>>>>>> return view(request, *args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\site-packages\djblets\webapi\resources\base.py", >>>>>>>>>>>> line 470, in post >>>>>>>>>>>> return self.create(*args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "build/bdist.macosx-10.11-x86_64/egg/rbpowerpack/extension/hooks.py", >>>>>>>>>>>> line 83, in _api_create_review_request >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\python\lib\site-packages\djblets\webapi\decorators.py", >>>>>>>>>>>> line 125, in _call >>>>>>>>>>>> return view_func(*args, **kwargs) >>>>>>>>>>>> File >>>>>>>>>>>> "C:\App\Bitnami\reviewboardpowerpack-3.0.12-1\apps\reviewboardpowerpack\htdocs\Lib\site-packages\ReviewBoard-3.0.12-py2.7.egg\reviewboard\webapi\decorators.py", >>>>>>>>>>>> line 169, in _check >>>>>>>>>>>> return view_func(*args, **kwargs) >>>>>>>>>>>> File &qu >>>>>>>>>>>> >>>>>>>>>>>> -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/a3aef212-6852-4925-8404-62dc8cd816ddo%40googlegroups.com.
