Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August

Ilya Maximets writes: > On 1/24/24 13:13, Aaron Conole wrote: >> Ilya Maximets writes: >> >>> On 1/24/24 01:14, Jeremy Kerr wrote: >>>> Hi Ilya, >>>> >>>>> Jeremy, could you, please, try to unban the robot? >>>> &

Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August

Ilya Maximets writes: > On 1/24/24 01:14, Jeremy Kerr wrote: >> Hi Ilya, >> >>> Jeremy, could you, please, try to unban the robot? >> >> Sure thing, done! > > Thanks! > >> >> Let me know how it goes on your side, I'll monitor things here. > > We'll re-enable the robot later today and will

Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August

Jeremy Kerr writes: > Hi Ilya, > >> Jeremy, could you, please, try to unban the robot? > > Sure thing, done! > > Let me know how it goes on your side, I'll monitor things here. Thanks. I've just re-enabled it. The first run will be noisy (because it will requery the open checks). After that,

Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August

Jeremy Kerr writes: > Hi Ilya, > >> Ugh.  Yeah, the checks/ requests are definitely something we can >> improve. Aaron is working on removing vast majority of this type of >> requests as we speak.  Hopefully, that will be done soon. > > OK, sounds good! > >> Do you think it'll be fine to unban

Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August

Jeremy Kerr writes: > Hi Ilya, > >> Ugh.  Yeah, the checks/ requests are definitely something we can >> improve. Aaron is working on removing vast majority of this type of >> requests as we speak.  Hopefully, that will be done soon. > > OK, sounds good! > >> Do you think it'll be fine to unban

Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August

Ilya Maximets writes: > On 1/22/24 14:59, Jeremy Kerr wrote: >> Hi Ilya, >> >>> We have a robot running in the RH network that pushes checks and >>> updates statuses for openvswitch and ovn projects, but it shouldn't >>> really make any "global patches view" types of requests.  All the >>>

Re: Adding custom tags like bugzilla id to patches

Don Zickus writes: > On Wed, Jan 03, 2018 at 11:23:43AM +1100, Andrew Donnellan wrote: >> On 03/01/18 08:31, Don Zickus wrote: >> > I wanted to add a custom tag to patchwork, for example 'Bugzilla:' that >> > would store the bugzilla id. This id could be queried later and

Re: Patchwork v2.0.0 Available

David Miller writes: > From: Michael Ellerman > Date: Mon, 28 Aug 2017 20:12:49 +1000 > >> Jeremy Kerr writes: >> >>> Hi all, >>> Just an update: the database migration for v2.0.0 is taking a *long* time, so we'll be out for

Re: [PATCH] parser: Log when invalid project list-id passed

Stephen Finucane writes: > I thought there was a bug. Turns out I was just using the wrong list-id. > Make this clearer. > > Signed-off-by: Stephen Finucane > --- > patchwork/parser.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH RFC] events-api: allow filtering by date

Andrew Donnellan <andrew.donnel...@au1.ibm.com> writes: > On 15/06/17 09:59, Daniel Axtens wrote: >> Aaron Conole <acon...@bytheb.org> writes: >> >>> Aaron Conole <acon...@bytheb.org> writes: >>> >>>> This commit allows users o

Re: [PATCH RFC] events-api: allow filtering by date

Aaron Conole <acon...@bytheb.org> writes: > This commit allows users of the REST API to query for events based on > the date field. This will allow utility writers to select a smaller > subset of events when polling. > > Signed-off-by: Aaron Conole <acon...@bytheb.org>

[PATCH RFC] events-api: allow filtering by date

This commit allows users of the REST API to query for events based on the date field. This will allow utility writers to select a smaller subset of events when polling. Signed-off-by: Aaron Conole <acon...@bytheb.org> --- patchwork/api/filters.py | 2 +- 1 file changed, 1 insertion

Server Error (500) starting with 02f8c2818bfd

Commit 02f8c2818bfd ("htdocs: Add clipboard.js") has caused my patchwork instance to start throwing server error. I am not sure which logs to look at (because /var/log/httpd/error_log doesn't seem to get updated right now). I'm using Firefox 53.0.3 to access the server. Server is running:

Re: [PATCH] migrations: Mark '0016_series_project' as non-atomic

Stephen Finucane <step...@that.guru> writes: > This should resolve migration issues arising from PostgreSQL's inability > to mix data and schema migrations in a single transaction. > > Signed-off-by: Stephen Finucane <step...@that.guru> > Closes-bug: #104 > Cc: Aa

Re: pending triggers error with 'manage.py migrate'

Hi Stephen, Stephen Finucane <step...@that.guru> writes: > On Mon, 2017-06-12 at 12:53 -0400, Aaron Conole wrote: >> I'm trying to upgrade an older patchwork instance I have, and it seems >> to be failing when I do a 'migrate' with the specific error: >> >>

pending triggers error with 'manage.py migrate'

I'm trying to upgrade an older patchwork instance I have, and it seems to be failing when I do a 'migrate' with the specific error: django.db.utils.OperationalError: cannot ALTER TABLE "patchwork_series" because it has pending trigger events I've made sure to update django-filter and