Re: pylint run
Hi Varun, The problem you're describing is not related to Review Board. The pylint website (http://www.pylint.org/) lists many support channels, you will be better off asking there. Adam On 1 Jun 2013, at 08:59, Varun Jain wrote: > Hi All, > > I want to check my all ReviewBoard automated scripts using pylint & wish to > encorporate changes to get (10.0/10) code rating for each file. > > Currently I am able to run pylint on two files only since rest of the files > are using try blocks & the pylint I am running says that 'as' is still not > the reserved keyword in > > python2.5 though I am using python2.7 to run my scripts. > > How can I make sure that the pylint I am using is compatible with python2.7 ?? > > I am running pylint from /opt/software/bin/pylint. > > Thanks, > Varun > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~--~~~~--~~--~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en > --- > 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/groups/opt_out. > > -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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/groups/opt_out.
Re: ReviewBoard is taking a nap on localhost
It's called python-memcache in Ubuntu. > On 5 Dec 2013, at 14:27, Stephen Gallagher wrote: > >> On 12/05/2013 05:27 AM, Christian Hammond wrote: >> python-memcached is separate from memcached itself. It's just a Python >> module for talking to a memcached server. >> >> I don't know whether yum has it, but you can use easy_install: >> >>sudo easy_install -U python-memcached > > Yum would have it (trust me :) ), but earlier in the thread, he > mentioned that he was on Ubuntu 12.04. I suspect that it may be named > differently in Ubuntu. Given the "E: Package 'python-memcached' has no > installation candidate", I suspect it was probably renamed to something > like python2-memcached, but not all dependent packages were updated. > > This is speculation, of course. > > -- > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ > --- > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ > --- > Happy user? Let us know at http://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/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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/groups/opt_out.
Re: OperationalError: database is locked
Hi Joe,
What database are you using for this? I would guess SQLite from the error.
That's not advisable for anything but a test/dev setup (you should use
PostgreSQL or MySQL in production)
Regards, Adam
> On 10 Apr 2014, at 17:30, Joe wrote:
>
> Hello,
>
> We periodically get this lock error. Im running review board 1.7.22.
>
> Best regards,
> Joe.
>
> --
>
> Traceback (most recent call last):
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/core/handlers/base.py",
> line 111, in get_response
> response = callback(request, *callback_args, **callback_kwargs)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Djblets-0.7.28-py2.6.egg/djblets/auth/util.py",
> line 47, in _checklogin
> return view_func(request, *args, **kwargs)
>
> File
> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/site/decorators.py",
> line 35, in _check
> return view_func(request, local_site=local_site, *args, **kwargs)
>
> File
> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/accounts/decorators.py",
> line 53, in _check_valid_prefs
> return view_func(request, *args, **kwargs)
>
> File
> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/reviews/views.py",
> line 828, in dashboard
> 'sidebar_counts': get_sidebar_counts(request.user, local_site),
>
> File
> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/reviews/datagrids.py",
> line 803, in get_sidebar_counts
> profile=profile)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/fields/related.py",
> line 493, in get_or_create
> return super(RelatedManager, self.db_manager(db)).get_or_create(**kwargs)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/manager.py",
> line 134, in get_or_create
> return self.get_query_set().get_or_create(**kwargs)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/query.py",
> line 452, in get_or_create
> obj.save(force_insert=True, using=self.db)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/base.py",
> line 463, in save
> self.save_base(using=using, force_insert=force_insert,
> force_update=force_update)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/base.py",
> line 555, in save_base
> transaction.commit_unless_managed(using=using)
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/transaction.py",
> line 135, in commit_unless_managed
> connection.commit_unless_managed()
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/backends/__init__.py",
> line 214, in commit_unless_managed
> self._commit()
>
> File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/backends/__init__.py",
> line 50, in _commit
> return self.connection.commit()
>
> OperationalError: database is locked
>
>
> path:/reviews/dashboard/,
> GET:,
> POST:,
> COOKIES:{'collapsediffs': 'True',
> 'csrftoken': '5a764b26f0910188c3e86cf96567dea7',
> 'rbsessionid': '6880c2e09e0002d305c304b9282eb587'},
> META:{'AUTH_TYPE': None,
> 'CONTENT_LENGTH': 0,
> 'CONTENT_TYPE': None,
> 'GATEWAY_INTERFACE': 'CGI/1.1',
> 'HTTP_ACCEPT':
> 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
> 'HTTP_ACCEPT_ENCODING': 'gzip, deflate',
> 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
> 'HTTP_CONNECTION': 'keep-alive',
> 'HTTP_COOKIE': 'rbsessionid=6880c2e09e0002d305c304b9282eb587;
> csrftoken=5a764b26f0910188c3e86cf96567dea7; collapsediffs=True',
> 'HTTP_HOST': 'daytona',
> 'HTTP_REFERER': 'http://daytona/reviews/account/preferences/',
> 'HTTP_USER_AGENT': 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0)
> Gecko/20100101 Firefox/23.0',
> 'PATH_INFO': u'/reviews/dashboard/',
> 'PATH_TRANSLATED': None,
> 'QUERY_STRING': None,
> 'REMOTE_ADDR': '172.16.56.188',
> 'REMOTE_HOST': None,
> 'REMOTE_IDENT': None,
> 'REMOTE_USER': None,
> 'REQUEST_METHOD': 'GET',
> 'SCRIPT_NAME': '',
> 'SERVER_NAME': 'daytona.us.megatrends.com',
> 'SERVER_PORT': 80,
> 'SERVER_PROTOCOL': 'HTTP/1.1',
> 'SERVER_SOFTWARE': 'mod_python'}>
> --
> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
> ---
> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
> ---
> Happy user? Let us know at http://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.
--
Get the Review Board Power Pack at http:/
Re: ReviewBoard now charmed for Juju
Hi Christian, It wouldn't hurt to get some eye balls on the code. Very much in its infancy but I have grand plans to add more awesomeness so want a solid starting point. I made the logo in SVG by hand copying the one on the site. Is that ok? Is there an official logo you'd like me to use instead? One idea is to allow people to configure repositories using the charm. The idea being to encapsulate the logic for each hosting service and make it as easy as possible for someone to try Review Board with their existing projects. Not quite sure how I might do that in the charm, but good to have something to aim for! Adam PS thanks for Review Board, used it happily for a number of years. Unfortunately haven't convinced my colleagues of it's superiority just yet, but give me time! > On 11 Jun 2014, at 23:47, Christian Hammond wrote: > > Hey Adam, > > Very cool! Anything you need from us for this? > > Christian > > -- > Christian Hammond - christ...@beanbaginc.com > Review Board - http://www.reviewboard.org > Beanbag, Inc. - http://www.beanbaginc.com > >> On June 11, 2014 at 1:20:36 PM, adam.coll...@gmail.com >> (adam.coll...@gmail.com) wrote: >> >> Hi, >> >> For the past couple of days I've been working on a Juju[1] Charm for Review >> Board, which I'm happy to announce has just been approved and released into >> the official Charm Store[2]. >> >> For those of you who aren't aware, Juju is a service orchestration >> technology which makes it really easy to configure, manage and maintain >> services both in a cloud environment and on regular servers. (disclosure: I >> work for Canonical who initiated Juju and are the driving force behind it) >> >> Deploying Review Board using Juju is now a few simple steps, and can be >> backed by EC2, OpenStack, Azure, HP Cloud, your data centre or scale down to >> containers on your Ubuntu laptop. >> >> This first release only works with PostgreSQL but I plan to extend it to add >> support for MySQL too. The more I think about it, the more extra bells and >> whistles I'd like to add. If anyone wants to join in and help out, I'll >> welcome your support with open arms. >> >> Adam Collard >> >> [1] https://juju.ubuntu.com/charms/ >> [2] https://jujucharms.com/sidebar/search/precise/reviewboard/ >> -- >> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ >> --- >> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ >> --- >> Happy user? Let us know at http://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. > -- > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ > --- > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ > --- > Happy user? Let us know at http://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. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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: Requested revision does not exist, using Bazaar
Hi Brian, Have you tried using the bzr-diff-revid plugin for Bazaar? https://launchpad.net/bzr-diff-revid >From the description on the LP page: "bzr-diff-revid is a plugin for the Bazaar VCS. It tweaks the output of "bzr diff": When possible, it includes the revid of the file version in the diff header, instead of the timestamp. This works with Review Board's bzr support to make diff loading reliable" When using bzr with ReviewBoard I found this plugin avoids the very issues you describe. Adam > On 17 Jun 2014, at 22:41, Brian wrote: > > My hope at this point is that there was something wrong with the repository. > We've used this combination of tools for a couple of years with no issue, > even after a couple of server upgrades/reinstalls. > >> On Tuesday, June 17, 2014 12:12:47 PM UTC-7, Christian Hammond wrote: >> Hi Brian, >> >> So, I guess Bazaar requires a local timestamp when doing a 'date:’ query. >> Review Board attempts to convert the date in the diff to a local date that >> would match it. It sounds like something’s going terribly wrong there. I >> toyed with it briefly, but couldn’t reproduce the problem you’re hitting. >> >> Christian >> >> -- >> Christian Hammond - chri...@beanbaginc.com >> Review Board - http://www.reviewboard.org >> Beanbag, Inc. - http://www.beanbaginc.com >> >>> On June 17, 2014 at 12:07:13 PM, Brian (phxg...@gmail.com) wrote: >>> >>> Hi Christian, >>> >>> So far I haven't found a pattern in the timestamps that are causing issues. >>> I have upgraded one of our servers to use RB 2.0.2 and I also recreated the >>> Bazaar repository that we were using. There are only two of us working on >>> this project and very little history, so we didn't really lose anything. >>> I'm hoping that our problem either goes away, or I will be able to find >>> something when I check a diff after each commit we do. >>> >>> I'll keep you up to date on what I can find out. >>> >>> Thanks for looking into this! >>> Brian >>> On Tuesday, June 17, 2014 3:40:28 AM UTC-7, Christian Hammond wrote: Hi Brian, Spent a little bit of time this evening trying to debug this, but no real luck. Can you see if there’s anything in common with the timestamps where things fail? Do they wrap around to a new day, new month, anything? Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com > On June 12, 2014 at 3:44:13 PM, Brian (phxg...@gmail.com) wrote: > > I can tell you what we know so far. When we have this issue, I trace the > "bad revision" back to what I can find in the Bazaar log for the file. We > are UTC-7, and the timestamp is usually 7 hours off from a match. This > may be the case for all files/revisions, I'm not sure yet. Most (if not > all) of our development machines are set to UTC, but maybe there is one > somewhere that is not and is affecting this. Typically we can edit the > diff to match the time in the bzr log and Review Board handles the diff > with no problem. > > In the last week, we have see an instance or two where this workaround > has not been successful. > > Separate, but maybe related, we have also had a couple of instances where > 1 of 24, or 2 of 6, or 4 of 4 diffs in a file did not apply cleanly. > We're not sure what happened with that exactly, but the timestamps in the > diff and log were off by 7 hours in those files too. > > I'm actually waiting for my IT person to make a copy of our server > template right now so I can debug this. I'm planning on getting things > set up to (hopefully) recreate the issue, then will try new versions of > Review Board to see if that helps any. If not, I'll look into creating a > clean Bazaar repository to see if that helps any. > > I'm also open to any other ideas you may have! > > Thanks, > Brian > >> On Thursday, June 12, 2014 3:26:31 PM UTC-7, Christian Hammond wrote: >> Hi Brian, >> >> Can you go into more details on how the timestamps affect things? I’d >> love to find a way to fix/workaround this in RBTools and/or Review Board. >> >> Christian >> >> -- >> Christian Hammond - chri...@beanbaginc.com >> Review Board - http://www.reviewboard.org >> Beanbag, Inc. - http://www.beanbaginc.com >> >>> On June 12, 2014 at 3:23:28 PM, Brian (phxg...@gmail.com) wrote: >>> >>> Hi Rahul, >>> >>> The way we have worked around it so far is to manually edit the diff. >>> We find the timestamp in the bzr log that it "should" be (UTC in our >>> case), then edit the diff to match. This had been ok for a while but it >>> is not working more and more often now. I'm actually about to start >>> debugging it a little more,
