DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Adam Hassick <ahassick@iol.unh.edu>
Cc: Patrick Robb <probb@iol.unh.edu>,
	 ci@dpdk.org,  dev <dev@dpdk.org>,
	Ali Alnubani <alialnu@nvidia.com>,
	 "Brandes, Shai" <shaibran@amazon.com>,
	 zhoumin <zhoumin@loongson.cn>,
	 "Puttaswamy, Rajesh T" <rajesh.t.puttaswamy@intel.com>
Subject: Re: Polling for patchseries in DPDK - the /series/ and /events/ endpoints
Date: Fri, 11 Jul 2025 08:25:22 -0400	[thread overview]
Message-ID: <f7tikjyoqx9.fsf@redhat.com> (raw)
In-Reply-To: <CAC-YWqh58peBbfAMV0TZ+i=dfsApCXKGgMfOV3LbvX-H4gtS-w@mail.gmail.com> (Adam Hassick's message of "Thu, 10 Jul 2025 16:11:41 -0400")

Adam Hassick <ahassick@iol.unh.edu> writes:

> Hi All,
>
> It appears that there already is a filter for projects for events, but
> the filter is configured to be hidden from the HTML view for some
> reason. We don't need to make any code changes to enable this feature.
> See here: https://github.com/getpatchwork/patchwork/blob/stable/3.2/patchwork/api/filters.py#L239
>
> If you visit the following URL:
> https://patchwork.dpdk.org/api/events/?category=series-created&project=CI
> You can filter for series created events by project. This query
> filters for series created events for the CI repo's project.

Thanks Adam - I was using the html view to discover the REST details
rather than looking at the filter setup.

> Adam
>
> On Fri, May 30, 2025 at 12:07 PM Patrick Robb <probb@iol.unh.edu> wrote:
>>
>> I went looking through recent series on patchwork and I think this
>> is a good example of the timestamp condition:
>> https://patchwork.dpdk.org/api/series/35145/. Looks like the
>> original commits were made on April 18, then the newest version was
>> submitted on May 5 but the series record retains the 4/18 date.
>>
>> And I see that there is no project filter provided by the /events/ endpoint. https://patchwork.dpdk.org/api/events/
>>
>> Adam, would you agree the project filter for API requests is pretty low hanging fruit? Seems like a common sense improvement to me.
>>
>> On Tue, May 6, 2025 at 3:08 PM Patrick Robb <probb@iol.unh.edu> wrote:
>>>
>>> Thanks for the clarification regarding the datetimes. Yes let's clear up any remaining questions offline at Prague. :)


      reply	other threads:[~2025-07-11 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 16:08 Patrick Robb
2025-05-06 14:12 ` Aaron Conole
2025-05-06 19:08   ` Patrick Robb
2025-05-30 16:02     ` Patrick Robb
2025-07-10 20:11       ` Adam Hassick
2025-07-11 12:25         ` Aaron Conole [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7tikjyoqx9.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=ahassick@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=probb@iol.unh.edu \
    --cc=rajesh.t.puttaswamy@intel.com \
    --cc=shaibran@amazon.com \
    --cc=zhoumin@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).