[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#955268: udd watch: "429 too many requests" from GitHub



Le 24/04/2020 à 15:57, Lucas Nussbaum a écrit :
> On 24/04/20 at 15:06 +0200, Johannes Schauer wrote:
>> Hi,
>>
>> On Mon, 30 Mar 2020 08:49:33 +0200 Xavier <yadd@debian.org> wrote:
>>> Le 30/03/2020 à 08:25, Lucas Nussbaum a écrit :
>>>> On 29/03/20 at 23:52 +0200, Adam Borowski wrote:
>>>>> On Sun, Mar 29, 2020 at 05:53:11PM +0200, Xavier wrote:
>>>>>>>>> IIRC with an access token the limit is 5000 queries per hour.  Without a
>>>>>>>>> token, much, much less.
>>>>>>>>
>>>>>>>> The UDD code calls uscan. Is there a way for uscan to use an access
>>>>>>>> token?
>>>>>>>
>>>>>>> not for now, but I can add this feature. Just to insert an additional
>>>>>>> header ?
>>>>>>
>>>>>> This little diff adds --http-header option. To use it:
>>>>>>
>>>>>> uscan --http-header=Access-Token=qwertyuiop
>>>>>>
>>>>>> Sounds good for you ?
>>>>
>>>> Yes, thanks!
>>>
>>> Done: https://salsa.debian.org/debian/devscripts/-/merge_requests/181
>>
>> since there is only little progress on that merge request, could we have an
>> intermediate solution? For example by severely reducing the rate with which
>> uscan is run on github.com? Even if this means that there is only a check done
>> once a week, that's better than the current situation which already persists
>> for over a month.
> 
> I think that a suitable workaround would be to have a local uscan copy
> in UDD that can add the header, and then modify UDD to use it for
> github.
> 
> Anybody with access to UDD can do it. If nobody does, I'll try to do it
> when I run into Debian time, which is scarse those days.

Hi,

Prefer to compile a 2.20.3~alpha of devscripts to avoid problems with
Perl path (modified code is in /usr/share/perl5/Devscripts/Uscan/)

To use it (with last changes:
  uscan --http-header=https://github.com@GitHubToken=value

Token will be sent only to URL starting with https://github.com. Then
this option can be set by default. Use --verbose to see what happens

Cheers,
Xavier


Reply to: