Some reports have failed for 2026_07_01

[github-actions]

2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/drupal/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/drupal/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/magento/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/magento/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/wordpress/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/wordpress/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1k/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1k/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top10k/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top10k/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top100k/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top100k/a11yButtonName.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1m/numUrls.json
2026_07_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1m/a11yButtonName.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/drupal/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/drupal/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/magento/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/magento/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/wordpress/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/wordpress/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1k/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1k/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top10k/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top10k/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top100k/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top100k/cruxSmallCls.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1m/cruxFastDcl.json
2026_06_01 not found in body for https://cdn.httparchive.org/v1/static/reports/top1m/cruxSmallCls.json

See latest log in GitHub Actions

[max-ostapenko]

@tunetheweb some of the links show the data. Is the check broken?

[max-ostapenko]

Seems this one fails with RATE_LIMIT_THRESHOLD_EXCEED -https://console.cloud.google.com/monitoring/alerting/alerts/0.o95u4y24cr2u?project=httparchive.

Maybe we shift it to reading directly from GCS bucket?

[tunetheweb]

Yeah I thought it might be that but away at the moment so hadn’t a chance to look yet other than try a simple rerun.

Think I’d prefer to read it for the final location as an e2e test. Should be easy enough to add a pause to the script to avoid tripping this. Not like we care how long this check takes to run as it only runs once a month as a quick check since we missed the reports being missing before.

[max-ostapenko]

BTW It will be transparent when and which step failed during the e2e data pipeline run.
So we may even think of getting rid of this check.

[tunetheweb]

So we may even think of getting rid of this check.

Possibly, but let's keep it for now as a backup. I've added the delay in #1299

And during that I discovered the main issue: the API responds with gzipped response even with a simple curl command that doesn't say it accepts gzip in accept-encoding. That's why it couldn't find the date in the binary response! We probably should fix that and respond with uncompressed data in that case.

[max-ostapenko]

Yeah, I changed all files to gzipped

[tunetheweb]

Well I guess we haven’t had any complaints so far (apart from this one!). Wouldn’t surprise me if some people are going API or curl-style calls and get thrown by this though. But let’s deal with that if/when it happens.

Closing this now #1299 is merged which happens compression.