Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-16 Thread Lucas Nussbaum
Hi,

On 16/04/23 at 14:44 -0400, Federico Grau wrote:
> 
> fyi -
> 
> The code changes above appear to still be resulting in sf.net errors, or at
> least the `unixcw' package still reports Watch errors. 
> 
> 
> https://salsa.debian.org/qa/qa/commit/395d923257e954663156fa315142415f50d1be6a
> 
> https://qa.debian.org/developer.php?login=donfede%40casagrau.org

It's just that it hasn't been rechecked successfully yet (due to the
rate limiting, checking packages hosted on sourceforge.net takes a long
time).

You can check using:
select * from upstream where source='unixcw';

The last_check column should not be NULL.

> I contacted SourceForce support via email, per info on their contact web page.
> Expect an update to this bug with status as I hear more, or in about a week.
> 
> https://sourceforge.net/support

Thanks!

Lucas



Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-16 Thread Federico Grau

fyi -

The code changes above appear to still be resulting in sf.net errors, or at
least the `unixcw' package still reports Watch errors. 


https://salsa.debian.org/qa/qa/commit/395d923257e954663156fa315142415f50d1be6a

https://qa.debian.org/developer.php?login=donfede%40casagrau.org


I contacted SourceForce support via email, per info on their contact web page.
Expect an update to this bug with status as I hear more, or in about a week.

https://sourceforge.net/support


#
#
# Copy of email sent to sf.net 2023-04-16:

Hello sfnet_ops --

I am Fede Grau, contacting you on behalf of the Debian community.  We are
seeking support from SourceForge Ops with recent RSS feed rate limit changes.
In particular if an "IP exception" may be created for Debian "watch" checks
for package updates.


Reviewing the SourceForge Support Documentation we see there is now an RSS
feed rate limit of "one hit per feed per 30 minutes".  Unfortunately this is
adversely affecting the Debian "watch" checks for updates of Free and Open
Source Software (FOSS) packages hosted at SourceForge.  The Debian project is
tracking this issue with Bug #1033632 .

https://sourceforge.net/p/forge/documentation/RSS/

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033632



As noted above, we're checking if an IP exception may be created for RSS feed
checks for the Debian project.  The qa.debian.org host performing the "watch"
checks very rarely changes IP address and is in the Debian IP range of:
x.x.x.x/x .  Feedback or questions are welcome.  Thanks for your
assistance.


I happen to be one of the package maintainers for the `unixcw' FOSS package
hosted at SourceForge, which has been affected by these RSS limits.

https://qa.debian.org/developer.php?login=donfede%40casagrau.org

https://unixcw.sourceforge.net/


regards,
donfede

Fede Grau




signature.asc
Description: PGP signature


Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-13 Thread Paul Wise
Control: retitle -1 qa.debian.org: sourceforge redirector for debian/watch 
files gets rate limited

On Thu, 2023-04-13 at 07:05 +0200, Lucas Nussbaum wrote:

> I added code to handle sf.net's rate limiting in the UDD importer, and
> triggered a refresh of all sf.net-hosted packages.

Excellent, thanks.

> I wonder if we should close this bug. The redirector has not been fixed
> (it will still hit rate limiting, but there's not much we can do about
> that); but the main path by which maintainers probably access watch data
> (UDD -> dashboards) has been fixed.

Federico Grau (CCed) was talking on #debian-mentors about contacting
SourceForge about increasing the rate limits for the Debian redirector
service, so lets leave the bug open for that process and discussion.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-12 Thread Lucas Nussbaum
On 13/04/23 at 08:29 +0800, Paul Wise wrote:
> On Wed, 2023-04-12 at 07:14 +0200, Lucas Nussbaum wrote:
> 
> > There's specific code in the UDD uscan wrapper[1] to handle github's
> > rate limiting. We could have something similar for either sf.net, or the
> > sf.net redirector. Before I work on that, it would be great if someone
> > could change the sf.net redirector to return 429 instead of 500 when
> > sf.net returns 429, so that this specific case is easier to identify.
> 
> This is now done, tested and deployed on the server:
> 
> https://salsa.debian.org/qa/qa/commit/395d923257e954663156fa315142415f50d1be6a
> 
> I elected to just pass on all SourceForge HTTP error codes,
> with the HTTP error text prefixed to clarify the error source.

Thanks!
I added code to handle sf.net's rate limiting in the UDD importer, and
triggered a refresh of all sf.net-hosted packages.

I wonder if we should close this bug. The redirector has not been fixed
(it will still hit rate limiting, but there's not much we can do about
that); but the main path by which maintainers probably access watch data
(UDD -> dashboards) has been fixed.

- Lucas

Some UDD notes for reference:
To watch the status of UDD trying to refresh all SF sources:
udd=> select status, count(*) from upstream where watch_file ~ 'sf.(net|php)' 
group by status;
status| count 
--+---
 newer package available  |   120
 up to date   |   469
 error|   976
 only older package available |53
(4 rows)

udd=> select warnings is null, count(*) from upstream where watch_file ~ 
'sf.(net|php)' group by 1;
 ?column? | count 
--+---
 f|   986
 t|   632
(2 rows)

To force a refresh of all sf.net sources:
update upstream set last_check = null where watch_file ~ 'sf.(php|net)' and 
warnings is not null;

- Lucas



Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-12 Thread Paul Wise
On Wed, 2023-04-12 at 07:14 +0200, Lucas Nussbaum wrote:

> There's specific code in the UDD uscan wrapper[1] to handle github's
> rate limiting. We could have something similar for either sf.net, or the
> sf.net redirector. Before I work on that, it would be great if someone
> could change the sf.net redirector to return 429 instead of 500 when
> sf.net returns 429, so that this specific case is easier to identify.

This is now done, tested and deployed on the server:

https://salsa.debian.org/qa/qa/commit/395d923257e954663156fa315142415f50d1be6a

I elected to just pass on all SourceForge HTTP error codes,
with the HTTP error text prefixed to clarify the error source.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-11 Thread Lucas Nussbaum
Hi,

On 12/04/23 at 09:16 +0800, Paul Wise wrote:
> On Wed, 2023-03-29 at 08:05 +0200, Christian Marillat wrote:
> 
> > For several days sf.php no longer works:
> > 
> > ,
> > > uscan warn: In watchfile debian/watch, reading webpage
> > >   https://qa.debian.org/watch/sf.php/synfig/ failed: 500 Error
> > `
> 
> This issue is caused by the underlying SourceForge infrastructure
> (their files RSS feed) starting to apply rate limiting and returning
> HTTP 429 Too Many Requests errors, which the Debian QA redirector
> easily hits, depending on how much use the service has per day.
> 
> We could have individual contributors rewrite every single one of their
> SourceForge debian/watch files to use the SourceForge files RSS feeds.
> 
> Alternatively we could move the code for the SourceForge redirector
> into uscan so that individual uscan users get separate rate limit
> buckets, rather than having one large Debian rate limit bucket.
> 
> Unfortunately these changes will not fix the problem of UDD getting
> errors all the time. To fix that, UDD would need to gain a distributed
> architecture with multiple IP addresses all contacting SourceForge.
> That may cause overloads of the SourceForge server resources though,
> which would probably lead to uscan getting blocked again.
> 
> So maybe we need to discuss this with SourceForge again.

There's specific code in the UDD uscan wrapper[1] to handle github's
rate limiting. We could have something similar for either sf.net, or the
sf.net redirector. Before I work on that, it would be great if someone
could change the sf.net redirector to return 429 instead of 500 when
sf.net returns 429, so that this specific case is easier to identify.

[1] https://salsa.debian.org/qa/udd/-/blob/master/rimporters/upstream.rb#L161

Lucas



Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-11 Thread Paul Wise
On Wed, 2023-03-29 at 08:05 +0200, Christian Marillat wrote:

> For several days sf.php no longer works:
> 
> ,
> > uscan warn: In watchfile debian/watch, reading webpage
> >   https://qa.debian.org/watch/sf.php/synfig/ failed: 500 Error
> `

This issue is caused by the underlying SourceForge infrastructure
(their files RSS feed) starting to apply rate limiting and returning
HTTP 429 Too Many Requests errors, which the Debian QA redirector
easily hits, depending on how much use the service has per day.

We could have individual contributors rewrite every single one of their
SourceForge debian/watch files to use the SourceForge files RSS feeds.

Alternatively we could move the code for the SourceForge redirector
into uscan so that individual uscan users get separate rate limit
buckets, rather than having one large Debian rate limit bucket.

Unfortunately these changes will not fix the problem of UDD getting
errors all the time. To fix that, UDD would need to gain a distributed
architecture with multiple IP addresses all contacting SourceForge.
That may cause overloads of the SourceForge server resources though,
which would probably lead to uscan getting blocked again.

So maybe we need to discuss this with SourceForge again.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-11 Thread Peter Blackman

On 06/04/2023 11:44, Christian Marillat wrote:

On 06 avril 2023 11:26, Peter B  wrote:


I think this problem is now resolved.
The big red ERROR texts in the Watch column on my DDPO page are slowly going 
away.

I don't know. I re-written my watch files to check sourceforge.net
instead of qa.debian.org

Christian


Hi Christian,

Seems I spoke too soon!  While uscan usually works when I try it locally,
now seems to fail randomly on my QA page.

Cheers,
Peter



Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-06 Thread Christian Marillat
On 06 avril 2023 11:26, Peter B  wrote:

> I think this problem is now resolved.
> The big red ERROR texts in the Watch column on my DDPO page are slowly going 
> away.

I don't know. I re-written my watch files to check sourceforge.net
instead of qa.debian.org

Christian



Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-04-06 Thread Peter B

I think this problem is now resolved.
The big red ERROR texts in the Watch column on my DDPO page are slowly going 
away.


Cheers,
Peter


On Wed, 29 Mar 2023 08:05:01 +0200 Christian Marillat  
wrote:
> Package: qa.debian.org
> Severity: normal
>
> Dear Maintainer,
>
> For several days sf.php no longer works:
>
> ,
> | uscan warn: In watchfile debian/watch, reading webpage
> | https://qa.debian.org/watch/sf.php/synfig/ failed: 500 Error
> `
>
> Christian
>
>



Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

2023-03-29 Thread Christian Marillat
Package: qa.debian.org
Severity: normal

Dear Maintainer,

For several days sf.php no longer works:

,
| uscan warn: In watchfile debian/watch, reading webpage
|   https://qa.debian.org/watch/sf.php/synfig/ failed: 500 Error
`

Christian