Open chillu opened 3 years ago
More research (after a single run through of UpdateAddons
(which creates thousands of BuildAddonsJob
)
SELECT COUNT(*) FROM QueuedJobDescriptor WHERE SavedJobMessages LIKE '%Could not parse version constraint%'\G;
*************************** 1. row ***************************
COUNT(*): 577
SELECT COUNT(*) FROM QueuedJobDescriptor WHERE SavedJobMessages LIKE '%Connection refused%'\G;
*************************** 1. row ***************************
COUNT(*): 345
SELECT COUNT(*) FROM QueuedJobDescriptor WHERE SavedJobMessages LIKE '%502 Bad Gateway%'\G;
*************************** 1. row ***************************
COUNT(*): 1091
At least the last two are likely related to rate limiting. It appears that silverstripe/frameworktest
is the first package which triggered one of these failures above. It's unclear how that influences subsequent job runs for completely different packages though. Might be some weird singleton reuse inside queuedjobs
From UAT, but have seen this in prod as well. It's building
a2nt/silverstripe-dropzone
here, but failing on a request forhttps://packagist.org/packages/silverstripe/frameworktest.json
. I think the 502 is packagist rate limiting us, since a standard GET (even from the same IP a while later) works fine. My theory is that the job data isn't passed through properly via queuedjobs.