Re: changing the host name / URL reference for reviewboard
Note that I did refer to an older article "How to change the site name of a particular reviewboard installation?" in the group from 2010, and wanted to ascertain that the steps mentioned there are sufficient enough for the newer versions as well. Thanks. Harish On Wednesday, 13 February 2019 10:02:47 UTC+5:30, harish varadarajan wrote: > > Hi, > > I want to understand the best practices to be followed when a given > ReviewBoard server name gets changed, but there are no other intended > changes. > Inputs in this regard will be highly helpful. > > The scenario is as below. > >- Unix host A which hosts RB instance (referred through http://A for >RB instance) is renamed as B. >- We cannot do host aliases, due to the restrictions that are in place. >- Is there an automatic method available in RB to account for this >change, and further propagate all other required changes and perform > checks. >- If not, post the host name change, will update to >/etc/http.d/conf.d/apache-wsgi.conf and restart of the apace server suffice >- Are there other DB related changes that needs to be performed, if a >manual change needs to be done. >- We do use memcached with hostname:port format. What will be the >changes required to handle this. >- Are there other changes required for Search / Search Index directory >structures >- Any other pointers or checks that needs to be performed. > > > Thanks ! > > > -- 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. For more options, visit https://groups.google.com/d/optout.
changing the host name / URL reference for reviewboard
Hi, I want to understand the best practices to be followed when a given ReviewBoard server name gets changed, but there are no other intended changes. Inputs in this regard will be highly helpful. The scenario is as below. - Unix host A which hosts RB instance (referred through http://A for RB instance) is renamed as B. - We cannot do host aliases, due to the restrictions that are in place. - Is there an automatic method available in RB to account for this change, and further propagate all other required changes and perform checks. - If not, post the host name change, will update to /etc/http.d/conf.d/apache-wsgi.conf and restart of the apace server suffice - Are there other DB related changes that needs to be performed, if a manual change needs to be done. - We do use memcached with hostname:port format. What will be the changes required to handle this. - Are there other changes required for Search / Search Index directory structures - Any other pointers or checks that needs to be performed. Thanks ! -- 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. For more options, visit https://groups.google.com/d/optout.
Upgrade to ReviewBoard 2.5.13.1
Hi, We intend to upgrade to RB 2.5.13.1 (from 2.5.6.1) and below is the list of steps that is intended to be followed on the day of migration. Please help review and let know if there is anything specific that needs to be accounted for the upgrade. (1) Create sql backup, using mysqldump. (2) Create backup of site directory. (3) easy_install -U ReviewBoard==2.5.13.1 (4) rb-site upgrade $site_dir (5) Validation of the server and checks for extensions. Thanks. -- Harish -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Mercurial + Got API Error 207 (HTTP code 400): The file was not found in the repository.
Hi,
we have a reviewboard setup for Mercurial and get the below error when
posting a review request.
Any inputs on this will be helpful.
>>> Got API Error 207 (HTTP code 400): The file was not found in the repository.
>>> Error data: {u'stat': u'fail', u'file': u'$file_name', u'err': {u'msg':
>>> u'The file was not found in the repository.', u'code': 207}, u'revision':
>>> u'$prev_revision'}
Traceback (most recent call last):
File "Python-2.7.5/bin/rbt", line 9, in
load_entry_point('RBTools==0.7.2', 'console_scripts', 'rbt')()
File
"Python-2.7.5/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/commands/main.py",
line 133, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
"Python-2.7.5/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/commands/__init__.py",
line 555, in run_from_argv
exit_code = self.main(*args) or 0
File
"Python-2.7.5/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/commands/post.py",
line 698, in main
(msg_prefix, e))
rbtools.commands.CommandError: Error validating diff
Information on RB, RBTools and Mercurial is as below.
Reviewboard version: 2.5.6.1
Mercurial version: 4.0.1
Reviewboard tools: RBTools 0.7.2
--
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
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: abort: The file was not found in the repository. (207)
Hi Divakar,
Was there a resolution to this issue.
We are encountering the same issue and any pointers on fixing this will be
helpful.
Thanks.
--
Harish
On Friday, 26 February 2016 20:51:16 UTC+5:30, Divakar K wrote:
>
> Can someone please able to help me to proceed further. its blocking.
>
> On Wednesday, 24 February 2016 17:46:28 UTC+5:30, Divakar K wrote:
>>
>> Attached mercurial repository configuration in reviewboard.
>>
>> On Wednesday, 24 February 2016 17:03:54 UTC+5:30, Divakar K wrote:
>>>
>>> Hi Christian,
>>>
>>> Please find the details as you asked.
>>>
>>> C:\HID\project-test\sis>rbt post --server
>>> http://reviewboard.test/reviews --submit-a
>>> s "test" --debug
>>> >>> RBTools 0.7.5 alpha 0 (dev)
>>> >>> Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit
>>> (Intel)]
>>> >>> Running on Windows-7-6.1.7601-SP1
>>> >>> Home = C:\Users\dkanagaraj\AppData\Roaming
>>> >>> Current directory = C:\HID\project-test\sis
>>> >>> Checking for a Subversion repository...
>>> >>> Unable to execute "svn help": skipping SVN
>>> >>> Checking for a Git repository...
>>> >>> Unable to execute "git --help" or "git.cmd --help": skipping Git
>>> >>> Checking for a Mercurial repository...
>>> >>> Running: hg root
>>> >>> Running: hg showconfig
>>> >>> Running: hg svn info
>>> >>> Command exited with rc 255: [u'hg', u'svn', u'info']
>>> hg: unknown command 'svn'
>>> Mercurial Distributed SCM
>>>
>>> basic commands:
>>>
>>> add add the specified files on the next commit
>>> annotate show changeset information by line for each file
>>> clone make a copy of an existing repository
>>> commitcommit the specified files or all outstanding changes
>>> diff diff repository (or selected files)
>>> exportdump the header and diffs for one or more changesets
>>> forgetforget the specified files on the next commit
>>> init create a new repository in the given directory
>>> log show revision history of entire repository or files
>>> merge merge another revision into working directory
>>> pull pull changes from the specified source
>>> push push changes to the specified destination
>>> removeremove the specified files on the next commit
>>> serve start stand-alone webserver
>>> statusshow changed files in the working directory
>>> summary summarize working directory state
>>> updateupdate working directory (or switch revisions)
>>>
>>> (use "hg help" for the full list of commands or "hg -v" for details)
>>> ---
>>> >>> Using candidate path u'default': u'ssh://
>>> h...@hg-che.aaitg.com/Chennai/sis'
>>> >>> repository info: Path: ssh://h...@hg-che.aaitg.com/Chennai/sis, Base
>>> path: , S
>>> upports changesets: False
>>> >>> Making HTTP GET request to http://reviewboard.test/reviews/api/
>>> >>> Running: hg branch
>>> >>> Running: hg -q outgoing --template {rev}\t{node|short}\t{branch}\n
>>> default -
>>> r .
>>> >>> Found outgoing changeset 75:9b67b2bd00f7
>>> >>> Running: hg log -r 75 --template {parents}
>>> >>> Running: hg parents --hidden -r 0
>>> >>> Running: hg identify -i --hidden -r 74 --config
>>> "extensions.rbtoolsnormalize
>>> =C:\Program Files
>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-0.7.5alpha0-p
>>> y2.7.egg\rbtools\helpers\hgext.py"
>>> >>> Running: hg identify -i --hidden -r 75 --config
>>> "extensions.rbtoolsnormalize
>>> =C:\Program Files
>>> (x86)\RBTools\Python27\lib\site-packages\rbtools-0.7.5alpha0-p
>>> y2.7.egg\rbtools\helpers\hgext.py"
>>> >>> Running: hg status --modified --added --removed --deleted
>>> >>> Running: hg -q outgoing --template {rev}\t{node|short}\t{branch}\n
>>> default -
>>> r 8d514d13b632
>>> >>> Command exited with rc 1: [u'hg', u'-q', u'outgoing', u'--template',
>>> u'{rev}
>>> \\t{node|short}\\t{branch}\\n', u'default', u'-r', u'8d514d13b632']
>>> ---
>>> >>> 0 outgoing changesets between remote and base.
>>> >>> Running: hg diff --hidden -r 8d514d13b632 -r 9b67b2bd00f7 --config
>>> "extensio
>>> ns.rbtoolsnormalize=C:\Program Files
>>> (x86)\RBTools\Python27\lib\site-packages\rb
>>> tools-0.7.5alpha0-py2.7.egg\rbtools\helpers\hgext.py"
>>> >>> Running: hg locate -r 8d514d13b632
>>> >>> Running: hg locate -r 9b67b2bd00f7
>>> >>> Making HTTP GET request to
>>> http://reviewboard.test/reviews/api/validation/diffs/
>>>
>>> >>> Cached response for HTTP GET
>>> http://reviewboard.test/reviews/api/validation/diff
>>> s/ expired and was modified
>>> >>> Making HTTP POST request to
>>> http://reviewboard.test/reviews/api/validation/diffs
>>> /
>>> >>> Got API Error 207 (HTTP code 400): The file was not found in the
>>> repository.
>>>
>>> >>> Error data: {u'stat': u'fail', u'file':
>>> u'RFP/hid-MS-PoC/start-script.sh', u
>>> 'err': {u'msg': u'The file was not found in the repository.', u'code':
>>> 207}, u'r
>>> evision': u'8d514d13b632'}
>>> Traceback (most recent call last):
>>> File
Re: rbt post within a mercurial repository does not work: API Error 207 file was not found
Hi,
We get a similar error with reviewboard while posting reviews for a change
in mercurial repository.
Is there a reason for occurrence of this type of error, and if yes, what
can possibly address this.
Thanks.
--
Harish
On Monday, 9 November 2015 22:35:09 UTC+5:30, Fabian Sturm wrote:
>
> Hi,
>
> I have a private reviewboard installation and added a remote mercurial
> repository with a url like this:
>
> ssh://user@servername/repositoryname
>
> I then created a new branch in my local clone of the repository and
> commited a change in a single (already existing) file.
> This new changeset is not yet pushed to the server.
>
> Now I do rbt post and get:
>
> ERROR: Error validating diff
>
> todo.txt: The file was not found in the repository. (HTTP 400, API Error
> 207)
>
> Any idea what is going wrong?
>
> Here the full output of rbt post -d
>
> $ rbt post -d
> >>> RBTools 0.7.5
> >>> Python 2.7.9 (default, Apr 2 2015, 15:33:21)
> [GCC 4.9.2]
> >>> Running on Linux-3.19.0-31-generic-x86_64-with-Ubuntu-15.04-vivid
> >>> Home = /home/sturm
> >>> Current directory = /home/sturm/hg/myrepo
> >>> Checking for a Subversion repository...
> >>> Unable to execute "svn help": skipping SVN
> >>> Checking for a Git repository...
> >>> Running: git rev-parse --git-dir
> >>> Command exited with rc 128: ['git', 'rev-parse', '--git-dir']
> fatal: Not a git repository (or any of the parent directories): .git
> ---
> >>> Checking for a Mercurial repository...
> >>> Running: hg root
> >>> Running: hg showconfig
> >>> Running: hg svn info
> >>> Command exited with rc 255: [u'hg', u'svn', u'info']
> hg: unknown command 'svn'
> Mercurial Distributed SCM
>
> basic commands:
>
> add add the specified files on the next commit
> annotate show changeset information by line for each file
> clone make a copy of an existing repository
> commitcommit the specified files or all outstanding changes
> diff diff repository (or selected files)
> exportdump the header and diffs for one or more changesets
> forgetforget the specified files on the next commit
> init create a new repository in the given directory
> log show revision history of entire repository or files
> merge merge working directory with another revision
> pull pull changes from the specified source
> push push changes to the specified destination
> removeremove the specified files on the next commit
> serve start stand-alone webserver
> statusshow changed files in the working directory
> summary summarize working directory state
> updateupdate working directory (or switch revisions)
>
> use "hg help" for the full list of commands or "hg -v" for details
> ---
> >>> Using candidate path u'default':
> u'ssh://user@servername/repositoryname'
> >>> repository info: Path: ssh://user@servername/repositoryname, Base
> path: , Supports changesets: False
> >>> Making HTTP GET request to http://myserver/reviewboard/api/
> >>> Running: hg branch
> >>> Running: hg -q outgoing --template {rev}\t{node|short}\t{branch}\n
> default -r .
> >>> Found outgoing changeset 2747:6164fc0ce839
> >>> Running: hg log -r 2747 --template {parents}
> >>> Running: hg parents --hidden -r 0
> >>> Running: hg identify -i --hidden -r 2730 --config
> extensions.rbtoolsnormalize=/home/sturm/.local/lib/python2.7/site-packages/rbtools/helpers/hgext.py
> >>> Running: hg identify -i --hidden -r 2747 --config
> extensions.rbtoolsnormalize=/home/sturm/.local/lib/python2.7/site-packages/rbtools/helpers/hgext.py
> >>> Running: hg status --modified --added --removed --deleted
> >>> Running: hg -q outgoing --template {rev}\t{node|short}\t{branch}\n
> default -r 2feedb453eac
> >>> Command exited with rc 1: [u'hg', u'-q', u'outgoing', u'--template',
> u'{rev}\\t{node|short}\\t{branch}\\n', u'default', u'-r', u'2feedb453eac']
> ---
> >>> 0 outgoing changesets between remote and base.
> >>> Running: hg diff --hidden -r 2feedb453eac -r 6164fc0ce839 --config
> extensions.rbtoolsnormalize=/home/sturm/.local/lib/python2.7/site-packages/rbtools/helpers/hgext.py
> >>> Running: hg locate -r 2feedb453eac
> >>> Running: hg locate -r 6164fc0ce839
> >>> Making HTTP GET request to
> http://myserver/reviewboard/api/validation/diffs/
> >>> Cached response for HTTP GET
> http://myserver/reviewboard/api/validation/diffs/ expired and was modified
> >>> Making HTTP POST request to
> http://myserver/reviewboard/api/validation/diffs/
> >>> Got API Error 207 (HTTP code 400): The file was not found in the
> repository.
> >>> Error data: {u'stat': u'fail', u'file': u'todo.txt', u'err': {u'msg':
> u'The file was not found in the repository.', u'code': 207}, u'revision':
> u'2feedb453eac'}
> Traceback (most recent call last):
> File "/home/sturm/.local/bin/rbt", line 11, in
> sys.exit(main())
> File
>
Re: Reviewboard 2.5.6.1 & comment severity
Hi Christian, Thanks for the inputs. Let me triage further on this and provide inputs on what and where is breaking. Based on your comments, if something was to break because of using collectstatic, I believe it has to be related only to extensions. Is my understanding correct. -- Harish On Tuesday, 6 September 2016 23:01:18 UTC+5:30, Christian Hammond wrote: > > You definitely should not need to run collectstatic, and doing so can > definitely break things in ways you may not have encountered yet. It's best > to forget that command exists. If static media is not working without it, > you have a bigger issue to solve on the server. > > Christian > > > On Tuesday, September 6, 2016, harish varadarajan <harish.va...@gmail.com > > wrote: > >> Hi Christian, >> >> reinstalling through easy_install and running install-static-media >> helped, though i had to run collectstatic to populate the static directory >> with the right contents for css / js and ext. >> The comment severity now shows up for the review comments. >> >> Thanks to the team at beanbag for the help and assistance. >> >> >> >> -- >> Harish >> >> On Tue, Sep 6, 2016 at 3:00 PM, Christian Hammond < >> christ...@beanbaginc.com> wrote: >> >>> The fact that the upgrade didn't complain about any evolutions being >>> required, but install-static-media did, is a bit of a red flag for me. I'm >>> not sure how you went about performing the migration between servers, but I >>> wouldn't have expected to see those errors... It could be preventing the >>> static media from installing. >>> >>> 1) When you say the css and js directories were not created under >>> static, do you mean $sitedir/htdocs/static? That would have been handled >>> under rb-site upgrade. >>> >>> Can you run: >>> >>> $ find $sitedir >>> >>> (Replace $sitedir, of course, with the path to the site directory, which >>> contains conf/ and htdocs/ and such.) >>> >>> >>> 2) How did you handle getting the new Python modules on the new server? >>> Did you copy them over, or reinstall? >>> >>> What I'm going to have you do is force a reinstall of the rbseverity >>> egg. First, we're going to ensure you have the latest version of pip: >>> >>> pip install -U pip >>> >>> Then, we're going to uninstall with pip, and re-install with >>> easy_install: >>> >>> pip uninstall pip >>> easy_install -U rbseverity >>> >>> The reason is that we don't currently ship wheels for rbseverity, just >>> eggs, and so we need easy_install for this. If you had previously installed >>> using pip, then things might not have been installed exactly right. Or, if >>> you copied over packages from the old server, it also might not have >>> installed right. >>> >>> You'll also want to do this for any other extension you have. >>> >>> >>> 3) Once you've done the above, re-run the install-extension-media >>> command, and then restart Apache. >>> >>> If that shows the "unapplied evolutions" again, we'll have to diagnose >>> that next. However, it's 2:30AM here, so I won't be up any longer. I'll be >>> around to look into this further tomorrow. >>> >>> >>> 4) Just as a sanity check, go into the Review Board admin page -> >>> Extensions and make sure none of the extensions are reporting any errors. >>> If they are, let me know which ones and what the error says. >>> >>> >>> Christian >>> >>> >>> -- >>> Christian Hammond >>> President/CEO of Beanbag <https://www.beanbaginc.com/> >>> Makers of Review Board <https://www.reviewboard.org/> >>> >>> On Tue, Sep 6, 2016 at 2:09 AM, harish varadarajan < >>> harish.varadara...@gmail.com> wrote: >>> >>>> Hi Christian, >>>> >>>> Thanks for the inputs. >>>> But, this didn't solve the issue. >>>> >>>> Log of rb-site upgrade: >>>> Rebuilding directory structure >>>> Updating database. This may take a while. >>>> >>>> The log output below, including warnings and errors, >>>> can be ignored unless upgrade fails. >>>> >>>> -- -- >>>> Creating tables ... >>>> There are unapplied evoluti
Re: Reviewboard 2.5.6.1 & comment severity
Hi Christian, reinstalling through easy_install and running install-static-media helped, though i had to run collectstatic to populate the static directory with the right contents for css / js and ext. The comment severity now shows up for the review comments. Thanks to the team at beanbag for the help and assistance. -- Harish On Tue, Sep 6, 2016 at 3:00 PM, Christian Hammond <christ...@beanbaginc.com> wrote: > The fact that the upgrade didn't complain about any evolutions being > required, but install-static-media did, is a bit of a red flag for me. I'm > not sure how you went about performing the migration between servers, but I > wouldn't have expected to see those errors... It could be preventing the > static media from installing. > > 1) When you say the css and js directories were not created under static, > do you mean $sitedir/htdocs/static? That would have been handled under > rb-site upgrade. > > Can you run: > > $ find $sitedir > > (Replace $sitedir, of course, with the path to the site directory, which > contains conf/ and htdocs/ and such.) > > > 2) How did you handle getting the new Python modules on the new server? > Did you copy them over, or reinstall? > > What I'm going to have you do is force a reinstall of the rbseverity egg. > First, we're going to ensure you have the latest version of pip: > > pip install -U pip > > Then, we're going to uninstall with pip, and re-install with easy_install: > > pip uninstall pip > easy_install -U rbseverity > > The reason is that we don't currently ship wheels for rbseverity, just > eggs, and so we need easy_install for this. If you had previously installed > using pip, then things might not have been installed exactly right. Or, if > you copied over packages from the old server, it also might not have > installed right. > > You'll also want to do this for any other extension you have. > > > 3) Once you've done the above, re-run the install-extension-media command, > and then restart Apache. > > If that shows the "unapplied evolutions" again, we'll have to diagnose > that next. However, it's 2:30AM here, so I won't be up any longer. I'll be > around to look into this further tomorrow. > > > 4) Just as a sanity check, go into the Review Board admin page -> > Extensions and make sure none of the extensions are reporting any errors. > If they are, let me know which ones and what the error says. > > > Christian > > > -- > Christian Hammond > President/CEO of Beanbag <https://www.beanbaginc.com/> > Makers of Review Board <https://www.reviewboard.org/> > > On Tue, Sep 6, 2016 at 2:09 AM, harish varadarajan < > harish.varadara...@gmail.com> wrote: > >> Hi Christian, >> >> Thanks for the inputs. >> But, this didn't solve the issue. >> >> Log of rb-site upgrade: >> Rebuilding directory structure >> Updating database. This may take a while. >> >> The log output below, including warnings and errors, >> can be ignored unless upgrade fails. >> >> -- -- >> Creating tables ... >> There are unapplied evolutions for webapi. >> Installing custom SQL ... >> Installing indexes ... >> Installed 0 object(s) from 0 fixture(s) >> No evolution required. >> --- --- >> >> Resetting in-database caches. >> >> Upgrade complete! >> >> Log of rb-site manage: >> There are unapplied evolutions for webapi. >> There are unapplied evolutions for webapi. >> There are unapplied evolutions for webapi. >> >> From the developer tools of chrome, for an already present review request: >> >> GET >> http://$site/static/ext/rbmotd.extension.MotdExtension/css/default.min.css >> 404 (Not Found) >> (index):796 GET http://$site/static/ext/rbseve >> rity.extension.SeverityExtension/js/severity-review.min.js >> (index):802 Uncaught ReferenceError: RBSeverity is not defined >> >> Post moving the previous static, and running rb-site manage $sitedir >> install-extension-media -- --force, I find that the directory structures >> css and js were not created under static. >> >> >> >> -- >> Harish >> >> On Tue, Sep 6, 2016 at 2:29 PM, Christian Hammond < >> christ...@beanbaginc.com> wrote: >> >>> Hi, >>> >>> rb-site upgrade manages the static media for Review Board itself, and >>> extensions missing static media files will have them copied from the >>> extension. >>> >>> Try erasing the contents of $sitedir/static
Re: Reviewboard 2.5.6.1 & comment severity
Hi Christian,
Thanks for the inputs.
But, this didn't solve the issue.
Log of rb-site upgrade:
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- --
Creating tables ...
There are unapplied evolutions for webapi.
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
No evolution required.
--- ---
Resetting in-database caches.
Upgrade complete!
Log of rb-site manage:
There are unapplied evolutions for webapi.
There are unapplied evolutions for webapi.
There are unapplied evolutions for webapi.
>From the developer tools of chrome, for an already present review request:
GET http://$site/static/ext/rbmotd.extension.MotdExtension/css/default.min.css
404 (Not Found)
(index):796 GET http://
$site/static/ext/rbseverity.extension.SeverityExtension/js/severity-review.min.js
(index):802 Uncaught ReferenceError: RBSeverity is not defined
Post moving the previous static, and running rb-site manage $sitedir
install-extension-media -- --force, I find that the directory structures
css and js were not created under static.
--
Harish
On Tue, Sep 6, 2016 at 2:29 PM, Christian Hammond <christ...@beanbaginc.com>
wrote:
> Hi,
>
> rb-site upgrade manages the static media for Review Board itself, and
> extensions missing static media files will have them copied from the
> extension.
>
> Try erasing the contents of $sitedir/static and then do:
>
> rb-site upgrade $sitedir
> rb-site manage $sitedir install-extension-media -- --force
>
> Christian
>
>
> On Tuesday, September 6, 2016, harish varadarajan <
> harish.varadara...@gmail.com> wrote:
>
>> Hi David,
>>
>> In our environment, we had moved the reviewboard instance from one server
>> to another, while as well upgrading versions from 2.0.15 to 2.5.6.1
>> Post setting up sql, apache, we had run rb-site install and moved over
>> the DB from older host to newer one, post which rb-site upgrade and rb-site
>> manage $site collectstatic was run.
>>
>> Considering the fact that now collectstatic has been run in a production
>> environment, and that comment severity is broken, is there a way to fix
>> this.
>> I believe copying of static contents from older server to newer one
>> should never be done and hence what would be the correct way to populate
>> these contents.
>>
>> Thanks.
>>
>> --
>> Harish
>>
>> On Monday, 5 September 2016 22:26:57 UTC+5:30, David Trowbridge wrote:
>>>
>>> Why are you running collectstatic? If you're installing from our
>>> pre-built packages, all the static media has already been compiled.
>>>
>>> -David
>>>
>>> On Mon, Sep 5, 2016 at 8:07 AM harish varadarajan <
>>> harish.va...@gmail.com> wrote:
>>>
>>>> Post installing reviewboard 2.6.6.1 and extension Comment Severity 0.5.1,
>>>> when trying to run collectstatic, the following error is seen.
>>>> The version of lessc is 2.7.1
>>>> File "/usr/lib/python2.7/site-packages/pipeline/compilers/__init__.py",
>>>> line 99, in execute_command
>>>> raise CompilerError(stderr)
>>>> pipeline.exceptions.CompilerError: NameError: variable @STATIC_ROOT is
>>>> undefined in /usr/lib/python2.7/site-packag
>>>> es/reviewboard/static/rb/css/pages/reviews.less on line 3, column 21:
>>>> 2 @import (reference) "../mixins/upload-diff.less";
>>>> 3 @import (reference) "@{STATIC_ROOT}djblets/css/mixins/markdown.less";
>>>>
>>>> I remember reading a post that lessc versions 2.X is not supported.
>>>> If yes, could this be the case of above failure ?
>>>> If not, what could cause this behavior. Any inputs on how to proceed
>>>> further / fix this, will be helpful.
>>>>
>>>> Thanks.
>>>>
>>>> Harish
>>>>
>>>>
>>>> --
>>>> 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 "reviewboard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to reviewboar
Re: Reviewboard 2.5.6.1 & comment severity
Hi David,
In our environment, we had moved the reviewboard instance from one server
to another, while as well upgrading versions from 2.0.15 to 2.5.6.1
Post setting up sql, apache, we had run rb-site install and moved over the
DB from older host to newer one, post which rb-site upgrade and rb-site
manage $site collectstatic was run.
Considering the fact that now collectstatic has been run in a production
environment, and that comment severity is broken, is there a way to fix
this.
I believe copying of static contents from older server to newer one should
never be done and hence what would be the correct way to populate these
contents.
Thanks.
--
Harish
On Monday, 5 September 2016 22:26:57 UTC+5:30, David Trowbridge wrote:
>
> Why are you running collectstatic? If you're installing from our pre-built
> packages, all the static media has already been compiled.
>
> -David
>
> On Mon, Sep 5, 2016 at 8:07 AM harish varadarajan <harish.va...@gmail.com
> > wrote:
>
>> Post installing reviewboard 2.6.6.1 and extension Comment Severity 0.5.1,
>> when trying to run collectstatic, the following error is seen.
>> The version of lessc is 2.7.1
>> File "/usr/lib/python2.7/site-packages/pipeline/compilers/__init__.py",
>> line 99, in execute_command
>> raise CompilerError(stderr)
>> pipeline.exceptions.CompilerError: NameError: variable @STATIC_ROOT is
>> undefined in
>> /usr/lib/python2.7/site-packages/reviewboard/static/rb/css/pages/reviews.less
>>
>> on line 3, column 21:
>> 2 @import (reference) "../mixins/upload-diff.less";
>> 3 @import (reference) "@{STATIC_ROOT}djblets/css/mixins/markdown.less";
>>
>> I remember reading a post that lessc versions 2.X is not supported.
>> If yes, could this be the case of above failure ?
>> If not, what could cause this behavior. Any inputs on how to proceed
>> further / fix this, will be helpful.
>>
>> Thanks.
>>
>> Harish
>>
>>
>> --
>> 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
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
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
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reviewboard 2.5.6.1 & comment severity
Post installing reviewboard 2.6.6.1 and extension Comment Severity 0.5.1,
when trying to run collectstatic, the following error is seen.
The version of lessc is 2.7.1
File "/usr/lib/python2.7/site-packages/pipeline/compilers/__init__.py",
line 99, in execute_command
raise CompilerError(stderr)
pipeline.exceptions.CompilerError: NameError: variable @STATIC_ROOT is
undefined in
/usr/lib/python2.7/site-packages/reviewboard/static/rb/css/pages/reviews.less
on line 3, column 21:
2 @import (reference) "../mixins/upload-diff.less";
3 @import (reference) "@{STATIC_ROOT}djblets/css/mixins/markdown.less";
I remember reading a post that lessc versions 2.X is not supported.
If yes, could this be the case of above failure ?
If not, what could cause this behavior. Any inputs on how to proceed
further / fix this, will be helpful.
Thanks.
Harish
--
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
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Changes with update diff in 2.5.6.1
Hi David, Thanks for the inputs. -- Harish On Sunday, 4 September 2016 22:57:24 UTC+5:30, David Trowbridge wrote: > > Harish, > > With the new UI, upload the review diff first. If Review Board detects > that it needs a parent diff, base directory, or commit ID, it will then > prompt you for them. > > -David > On Sun, Sep 4, 2016 at 1:40 AM harish varadarajan <harish.va...@gmail.com > > wrote: > >> The documentation of 2.5, >> https://www.reviewboard.org/docs/manual/2.5/users/review-requests/uploading-diffs/ >> does >> have information. >> Is there a way to mimic the older behavior ? >> >> Thanks. >> >> Harish >> >> >> On Sunday, 4 September 2016 13:51:26 UTC+5:30, harish varadarajan wrote: >>> >>> Hi, >>> >>> we recently updated to RB 2.5.6.1 from 2.0.15 and find a difference in >>> behavior for "Update" -> "Update diff" ( "Upload diff" )of reviews >>> while in 2.0.15, entries were present to have "Parent Diff" and "Base >>> commit id", this is not seen in 2.5.6.1 >>> >>> Is this the intended behavior. If not, what needs to be done to enable >>> the same. >>> How can a user now choose base revision with 2.5.6.1 >>> >>> Thanks. >>> >>> -- >>> Harish >>> >> -- >> 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 >> "reviewboard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to reviewboard...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Changes with update diff in 2.5.6.1
The documentation of 2.5, https://www.reviewboard.org/docs/manual/2.5/users/review-requests/uploading-diffs/ does have information. Is there a way to mimic the older behavior ? Thanks. Harish On Sunday, 4 September 2016 13:51:26 UTC+5:30, harish varadarajan wrote: > > Hi, > > we recently updated to RB 2.5.6.1 from 2.0.15 and find a difference in > behavior for "Update" -> "Update diff" ( "Upload diff" )of reviews > while in 2.0.15, entries were present to have "Parent Diff" and "Base > commit id", this is not seen in 2.5.6.1 > > Is this the intended behavior. If not, what needs to be done to enable the > same. > How can a user now choose base revision with 2.5.6.1 > > Thanks. > > -- > Harish > -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Changes with update diff in 2.5.6.1
Hi, we recently updated to RB 2.5.6.1 from 2.0.15 and find a difference in behavior for "Update" -> "Update diff" ( "Upload diff" )of reviews while in 2.0.15, entries were present to have "Parent Diff" and "Base commit id", this is not seen in 2.5.6.1 Is this the intended behavior. If not, what needs to be done to enable the same. How can a user now choose base revision with 2.5.6.1 Thanks. -- Harish -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"
Hi Christian, Thanks for the inputs . As updated in the other thread, copying over the SECRET_KEY from older instance to newer instance helped solve the problem, though the server logs & the error in itself were misleading. -- Harish On Sunday, 31 July 2016 01:50:16 UTC+5:30, Christian Hammond wrote: > > Hi Harish, > > Can you show me the entire stack trace from the reviewboard.log file? > > The database may have been set for UTF-8, but that doesn't mean the tables > or data was converted for that. If you look at the MySQL dump, you'll see > that each table specifies its encoding. By default for some installs, this > is latin1. > > It's not sufficient to simply change that in the database dump or set > character_set_database. You'll actually need to convert each table: > > ALTER TABLE CONVERT TO CHARACTER SET utf8 COLLATE > utf8_unicode_ci; > > That may not address this particular issue, though. I'll need a lot more > information to know what's breaking and how, and how your repro steps. > > Christian > > -- > Christian Hammond > President/CEO of Beanbag <https://www.beanbaginc.com/> > Makers of Review Board <https://www.reviewboard.org/> > > On Fri, Jul 29, 2016 at 7:12 PM, harish varadarajan < > harish.va...@gmail.com > wrote: > >> Further, the reviewboard database was created with UTF8 character set. >> >> MariaDB [reviewboard]> show variables like "character_set_database"; >> ++---+ >> | Variable_name | Value | >> ++---+ >> | character_set_database | utf8 | >> >> The specific error from the server log seems to be >> >> DjangoUnicodeDecodeError: 'utf8' codec can't decode byte 0x8b in position >> 0: invalid start byte. You passed in > at 0x7f4caebd0fd0> () >> >> >> >> On Friday, 29 July 2016 20:26:38 UTC+5:30, harish varadarajan wrote: >>> >>> Hi, >>> >> >> >>> >>> I am pretty new to reviewboard and have attempted to migrate reviewboard >>> instance across hosts and versions. >>> Our older RB version was and the upgrade was to 2.5.6.1 >>> >>> Steps followed for the upgrade were >>> (1) Dump data on the older server (mysql) >>> (2) Drop the previously created reviewboard database, created by rb-site >>> install >>> (3) Manually create a database named reviewboard with UTF8 >>> (4) load the data from the mysql dump >>> (5) Run rb-site upgrade. >>> >>> Post the upgrade which completed successfully, the dashboard, contents >>> and other information came up properly, including the repository listing. >>> But, the issue is that neither the properties of repositories are >>> editable in newer instance nor or the older diff's from reviews accessible >>> . The creation of newer reviews for the repositories, which get imported >>> are as well not happening due to this.. >>> >>> While trying to access the repository from Manage -> Repositories -> >>> Select repository to change is as below. >>> Something broke! (Error 500) >>> >>> It appears something broke when you tried to go to here. This is either >>> a bug in Review Board or a server configuration error. Please report this >>> to your administrator. >>> >>> >>> Please note that the creation of newer repositories and using them for >>> review requests. >>> >>> >>> The errors in the server error log are similar to the ones below. >>> >>> Can someone please throw light on what the issue is and how it could be >>> fixed. >>> >>> >>> Unexpected error fetching file from $"http path of the file": 'ascii' >>> codec can't decode byte 0xfe in position 3: ordinal not in range(128) >>> >>> >>> - /usr/lib/python2.7/site-packages/django/forms/widgets.py:237: >>> UnicodeWarning: Unicode unequal comparison failed to convert both arguments >>> to Unicode - interpreting them as being unequal >>> if value != '': >>> >>> >>> Thanks. >>> >>> >>> Harish. >>> >> -- >> 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 >> "reviewboard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to reviewboard...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)
Hi Christian, Thanks for looking into this. As suggested by Eric, and per update in your mail, I copied over the SECRET_KEY, and restarted httpd, and now the repositories are accessible and also, the previous review requests created in the older server show up their diff's correcty, which was not the case before. Thanks for your inputs and certainly going over the contents in this group, help solved a lot of initial niggles. -- Harish On Sunday, 31 July 2016 01:43:53 UTC+5:30, Christian Hammond wrote: > > Ah, I see you have another thread on this. I'll respond there. > > Christian > > -- > Christian Hammond > President/CEO of Beanbag <https://www.beanbaginc.com/> > Makers of Review Board <https://www.reviewboard.org/> > > On Sat, Jul 30, 2016 at 1:12 PM, Christian Hammond <chri...@beanbaginc.com > > wrote: > >> Hi Harish, >> >> I'm not sure I fully understand what problems you're hitting, but a >> couple notes: >> >> 1) If you're using a database that was set up on an older instance, then >> yes, SECRET_KEY must be copied over. If it was not, a number of things like >> stored database passwords or hosting service auth tokens will be >> inaccessible. >> >> Entering a new password for each repository should take care of that. It >> sounds like you're hitting a problem doing this? Define "not editable?" >> >> 2) You should not have DEBUG = True on, for any reason, really. This is >> intended for development environments, and will alter behaviors that are >> not suitable for production environments. >> >> >> Can you describe what you're trying to do and exactly what's going wrong? >> >> Thanks, >> >> Christian >> >> -- >> Christian Hammond >> President/CEO of Beanbag <https://www.beanbaginc.com/> >> Makers of Review Board <https://www.reviewboard.org/> >> >> On Fri, Jul 29, 2016 at 7:34 PM, harish varadarajan < >> harish.va...@gmail.com > wrote: >> >>> Hi Eric, >>> >>> Thanks for your post, that I could understand the issue that was >>> happening at my reviewboard instance. >>> >>> Did you figure out the solution for this. >>> With your approach to turning the Debug = True, I am currently able to >>> access the repositories / enter the edit screen. >>> But unfortunately, the password field for the user who access on >>> repositories is not editable. >>> >>> But, still while creating newer reviews for older repositories, it >>> states that the content / change is not available. >>> Is the only way to make it work, is to copy the SECRET_KEY from the >>> older instance ? >>> any ideas on how this could be solved, if access to the older host / >>> instance is not available. >>> >>> Thanks. >>> >>> Harish >>> >>> On Thursday, 29 October 2015 12:19:12 UTC+5:30, er...@tibco.com wrote: >>>> >>>> I figured out what my issue was. Copying the database from one machine >>>> to another isn't sufficient. >>>> >>>> ReviewBoard has a "SECRET_KEY" that is used when encrypting passwords >>>> into the database. If you're restoring your database backup to a different >>>> machine (as I was doing), and you don't copy over the SECRET_KEY, then >>>> stuff will break. >>>> >>>> If you re-save the passwords from the web UI, it uses the SECRET_KEY >>>> when re-obfuscating the password. >>>> >>>> Might that be the problem? >>>> >>>> Eric. >>>> >>>> On Wednesday, October 28, 2015 at 9:56:15 AM UTC-7, er...@tibco.com >>>> wrote: >>>>> >>>>> Turns out I've been fighting this issue on and off for several days >>>>> now. >>>>> >>>>> This looks like it is one of those particularly evil bugs. I've >>>>> captured a lot of details about it below: >>>>> >>>>> Situation very similar - I'm using mysqldump to backup a database. In >>>>> my case, I'm trying to restore to a different machine for testing >>>>> purposes. >>>>> >>>>> When I bring up the test instance, I get an error 500 when I attempt >>>>> to examine the details of a configured repository. >>>>> >>>>> Email contains this (trimmed somewhat to avoid the long stack trace): >>>>> File "/usr/lib64/python2.7/site-pa
Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)
Hi Eric, Thanks for your post, that I could understand the issue that was happening at my reviewboard instance. Did you figure out the solution for this. With your approach to turning the Debug = True, I am currently able to access the repositories / enter the edit screen. But unfortunately, the password field for the user who access on repositories is not editable. But, still while creating newer reviews for older repositories, it states that the content / change is not available. Is the only way to make it work, is to copy the SECRET_KEY from the older instance ? any ideas on how this could be solved, if access to the older host / instance is not available. Thanks. Harish On Thursday, 29 October 2015 12:19:12 UTC+5:30, er...@tibco.com wrote: > > I figured out what my issue was. Copying the database from one machine to > another isn't sufficient. > > ReviewBoard has a "SECRET_KEY" that is used when encrypting passwords into > the database. If you're restoring your database backup to a different > machine (as I was doing), and you don't copy over the SECRET_KEY, then > stuff will break. > > If you re-save the passwords from the web UI, it uses the SECRET_KEY when > re-obfuscating the password. > > Might that be the problem? > > Eric. > > On Wednesday, October 28, 2015 at 9:56:15 AM UTC-7, er...@tibco.com wrote: >> >> Turns out I've been fighting this issue on and off for several days now. >> >> This looks like it is one of those particularly evil bugs. I've captured >> a lot of details about it below: >> >> Situation very similar - I'm using mysqldump to backup a database. In my >> case, I'm trying to restore to a different machine for testing purposes. >> >> When I bring up the test instance, I get an error 500 when I attempt to >> examine the details of a configured repository. >> >> Email contains this (trimmed somewhat to avoid the long stack trace): >> File "/usr/lib64/python2.7/site-packages/django/template/base.py", >> line 897, in render >> return render_value_in_context(output, context) >> >> File "/usr/lib64/python2.7/site-packages/django/template/base.py", >> line 875, in render_value_in_context >> value = force_text(value) >> >> File "/usr/lib64/python2.7/site-packages/django/utils/encoding.py", >> line 116, in force_text >> raise DjangoUnicodeDecodeError(s, *e.args) >> >> DjangoUnicodeDecodeError: 'utf8' codec can't decode byte 0xad in position >> 0: invalid start byte. You passed in > at 0x7effbb2e0510> () >> >> >> So, seems obvious - an encoding issue. Except, it isn't. >> >> I've been very careful to ensure that MySQL uses UTF-8 everywhere (on >> both production and testing). A mysqldump of the tables on the production >> database, and the test instance database shows that the scmtools_repository >> tables are *identical*, including the schema, and show use of UTF-8 as >> the charset. I even did a mysql --xml -e query of the tables, and found >> that they're identical. A hexdump of the results shows no non-ASCII >> characters. In fact, the only odd character is a 09 at the beginning of the >> password field (which looks to be intentional?). Mind you, this is as >> expected, because the password field looks to be a base64 encoding of an >> actual password, so it necessarily wouldn't encode any non-ASCII characters. >> >> I've confirmed that changing the password field using SQL, then resetting >> the password in the web UI makes the problem go away (for how long?). >> >> So now for the *really* messed up part. To try to get more / better >> diagnostics, I went to the "conf" folder for my ReviewBoard instance. I >> changed "Debug" flag to "True". Restart Apache (hosted via wsgi, FYI). >> >> Ready to look at details problem reports. Except ... problem gone >> >> I've now repeated this experiment several times. Set "Debug" to "False", >> problem occurs. "Debug = True", and problem goes away. >> >> This has all the classic signs of being an uninitialized variable. Arghhh. >> >> Any suggestions you have for further debugging would be most welcome. I >> fear that this is a bug in Django treatment of password fields. >> >> Eric. >> >> On Monday, December 22, 2014 at 4:53:35 AM UTC-8, Daniel Laird wrote: >>> >>> All, >>> >>> Since RB 1.5 I have backed up the RB installation everynight be by using >>> mysqldump user=x password=y reviewboard > backup.sql >>> >>> I have also backed up all attachments etc. >>> I could then restore the data easily with another script. >>> >>> I used this method to upgrade from 1.7.25 -> 2.0.11 and with the >>> additional rb-site upgrade etc, it all worked great. >>> However, after 2 days I noticed an error on my setup and re-created the >>> site and re-imported the data. >>> >>> At this point it was a RB 2.0.11 backup being restored to a RB2.0.11 >>> database. >>> It all appeared to go ok, but when I clicked on any review i got >>> Error 500, something broke, I also got the following email: >>> >>>
Re: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"
Further, the reviewboard database was created with UTF8 character set. MariaDB [reviewboard]> show variables like "character_set_database"; ++---+ | Variable_name | Value | ++---+ | character_set_database | utf8 | The specific error from the server log seems to be DjangoUnicodeDecodeError: 'utf8' codec can't decode byte 0x8b in position 0: invalid start byte. You passed in () On Friday, 29 July 2016 20:26:38 UTC+5:30, harish varadarajan wrote: > > Hi, > > > I am pretty new to reviewboard and have attempted to migrate reviewboard > instance across hosts and versions. > Our older RB version was and the upgrade was to 2.5.6.1 > > Steps followed for the upgrade were > (1) Dump data on the older server (mysql) > (2) Drop the previously created reviewboard database, created by rb-site > install > (3) Manually create a database named reviewboard with UTF8 > (4) load the data from the mysql dump > (5) Run rb-site upgrade. > > Post the upgrade which completed successfully, the dashboard, contents and > other information came up properly, including the repository listing. > But, the issue is that neither the properties of repositories are editable > in newer instance nor or the older diff's from reviews accessible . The > creation of newer reviews for the repositories, which get imported are as > well not happening due to this.. > > While trying to access the repository from Manage -> Repositories -> > Select repository to change is as below. > Something broke! (Error 500) > > It appears something broke when you tried to go to here. This is either a > bug in Review Board or a server configuration error. Please report this to > your administrator. > > > Please note that the creation of newer repositories and using them for > review requests. > > > The errors in the server error log are similar to the ones below. > > Can someone please throw light on what the issue is and how it could be > fixed. > > > Unexpected error fetching file from $"http path of the file": 'ascii' > codec can't decode byte 0xfe in position 3: ordinal not in range(128) > > > - /usr/lib/python2.7/site-packages/django/forms/widgets.py:237: > UnicodeWarning: Unicode unequal comparison failed to convert both arguments > to Unicode - interpreting them as being unequal > if value != '': > > > Thanks. > > > Harish. > -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"
Hi, I am pretty new to reviewboard and have attempted to migrate reviewboard instance across hosts and versions. Our older RB version was and the upgrade was to 2.5.6.1 Steps followed for the upgrade were (1) Dump data on the older server (mysql) (2) Drop the previously created reviewboard database, created by rb-site install (3) Manually create a database named reviewboard with UTF8 (4) load the data from the mysql dump (5) Run rb-site upgrade. Post the upgrade which completed successfully, the dashboard, contents and other information came up properly, including the repository listing. But, the issue is that neither the properties of repositories are editable in newer instance nor or the older diff's from reviews accessible . The creation of newer reviews for the repositories, which get imported are as well not happening due to this.. While trying to access the repository from Manage -> Repositories -> Select repository to change is as below. Something broke! (Error 500) It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator. Please note that the creation of newer repositories and using them for review requests. The errors in the server error log are similar to the ones below. Can someone please throw light on what the issue is and how it could be fixed. Unexpected error fetching file from $"http path of the file": 'ascii' codec can't decode byte 0xfe in position 3: ordinal not in range(128) - /usr/lib/python2.7/site-packages/django/forms/widgets.py:237: UnicodeWarning: Unicode unequal comparison failed to convert both arguments to Unicode - interpreting them as being unequal if value != '': Thanks. Harish. -- 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 "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
