pwclient can not filter by delegate

Andreas Bießmann andreas.devel at
Mon Mar 18 22:57:15 EST 2013

Hi Jeremy,

On 03/18/2013 01:52 AM, Jeremy Kerr wrote:
> Hi Andreas,
>> pwclient provides a '-d' switch to filter by delegate but this doesn't
>> work. It seems pwclient does a rpc.person_list() which unfortunately
>> does not contain the correct user id's. For example the id for my
>> 'delegate' user seems to be 6342, but the rpc.person_list() contains
>> some other uid's. For me this is 4656, 5830, 12555 and 14489 but not
>> 6342.
>> If I provide my uid as delegate_id I'll get the correct answer. So the
>> question is how to find the correct 'delegate users' via rpc.
> What's happening here is that you're seeing separate IDs for "user" (ie,
> someone with a patchwork account") and "person" (ie, someone who has
> submitted a patch or comment to patchwork). The person_list() method is
> returning the latter, but the delegate IDs are the former.
> Unfortunately, it doesn't look like there's a nice way to do this with
> the current XMLRPC API, but I'm happy to extend the interface to suit.
> Do you have any thoughts on which might be the best way to specify a
> delegate? By username, or real name (or both?)?

I think both would be good. I personally will use my username, cause it
is shorter than my real name. But the filter in web ui tells only the
real name, so for other users it is required to search by real name.

Another thing comes to mind here. It is not required for this use case
but how about a search for email(parts)? Some users may like to have a
tool to find delegates for lets say a specific domain.
On the other hand the 'people search' (person_list()) also gets a mail
substring. I think this is also good reason for some email related
interface here.

Best regards

Andreas Bießmann

More information about the Patchwork mailing list