You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 25, 2026. It is now read-only.
Hi. When running the nightly tests, we observed two occasions where requesting a search on Maven Central 1 leads to a HTTP Error 403 response 2, 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?
@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?
@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?
Activity
amotl commentedon Feb 26, 2026
While it was about 403's coming from
search.maven.orgbefore, it is aboutcentral.sonatype.com1 now 2.Footnotes
https://central.sonatype.com/solrsearch/select?q=a:antlr4-master+g:org.antlr ↩
https://github.com/crate/cratedb-sqlparse/actions/runs/22335703848/job/64627635351#step:6:40 ↩
amotl commentedon Feb 26, 2026
@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 commentedon Feb 26, 2026
@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 commentedon Feb 26, 2026
I can see this would apparently need to happen on behalf of the
antlr4-toolsPython package, specifically at those spots, right?surister commentedon Feb 26, 2026
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 commentedon Feb 26, 2026
Real issue is tracked at antlr/antlr4-tools#22
amotl commentedon Feb 28, 2026
It looks like this patch can heal CI already.
ANTLR4_TOOLS_ANTLR_VERSION=4.13.2#246amotl commentedon Mar 1, 2026
Other than the quick fix shared yesterday, this patch and report resembles a better solution, as suggested by @asuol. Thanks!
search.maven.organtlr/antlr4-tools#23antlr4-toolsthat usessearch.maven.org#247