Tests: HTTP Error 403: Forbidden

[amotl]

Hi. When running the nightly tests, we observed two occasions where requesting a search on Maven Central ¹ leads to a HTTP Error 403 response ², most probably because it (GitHub!) is hammering that API/endpoint a little bit too much at that particular time.

The problem can easily be fixed by re-running the CI job, so it's merely a cosmetic/convenience issue. However, the situation could possibly be improved on a regular maintenance cycle?

Footnotes

1. https://search.maven.org/solrsearch/select?q=a:antlr4-master+g:org.antlr ↩

2. https://github.com/crate/cratedb-sqlparse/actions/runs/14555490320/job/40831907691#step:5:66 ↩

[amotl]

While it was about 403's coming from search.maven.org before, it is about central.sonatype.com ¹ now ².

Footnotes

1.  https://central.sonatype.com/solrsearch/select?q=a:antlr4-master+g:org.antlr ↩

2.  https://github.com/crate/cratedb-sqlparse/actions/runs/22335703848/job/64627635351#step:6:40 ↩

[amotl]

@surister: Is it absolutely required to run a search request to Jar package registries like outlined above, or could this step be omitted and designed differently?

[amotl]

@surister: Can the Jar files be fetched through normal mechanisms, like other applications will also not run into rate limiting issues when pulling their Java dependencies into CI environments? Maybe it helps already to set or adjust the HTTP user agent on relevant requests?

[amotl]

Maybe it helps already to set or adjust the HTTP user agent?

I can see this would apparently need to happen on behalf of the antlr4-tools Python package, specifically at those spots, right?

[surister]

One could patch antlr4-tools, yes. Specifically https://github.com/antlr/antlr4-tools/blob/6e6a2a781277d7463369f5248275ee5e7c5eb997/antlr4_tool_runner.py#L47

Didn't do it in the past because typically, a re-run would just pass.

[surister]

Real issue is tracked at antlr/antlr4-tools#22

[amotl]

It looks like this patch can heal CI already.

• CI: Set environment variable ANTLR4_TOOLS_ANTLR_VERSION=4.13.2 #246

[amotl]

Other than the quick fix shared yesterday, this patch and report resembles a better solution, as suggested by @asuol. Thanks!

• Improvement: Adjust jar package search to use search.maven.org antlr/antlr4-tools#23
• Verification: CI: Install adjusted antlr4-tools that uses search.maven.org #247
• Report: Bad request on central.sonatype.com antlr/antlr4-tools#22 (comment)