Skip to content
This repository was archived by the owner on Jun 25, 2026. It is now read-only.
This repository was archived by the owner on Jun 25, 2026. It is now read-only.

Tests: HTTP Error 403: Forbidden #170

Closed

Description

@amotl

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?

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 ↩

Activity

  1. amotl commented on Feb 26, 2026

    @amotl
    ContributorAuthor

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

    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 ↩

  2. amotl commented on Feb 26, 2026

    @amotl
    ContributorAuthor

    @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?

  3. amotl commented on Feb 26, 2026

    @amotl
    ContributorAuthor

    @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?

  4. amotl commented on Feb 26, 2026

    @amotl
    ContributorAuthor

    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?

  5. surister commented on Feb 26, 2026

    @surister
    Contributor

    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.

  6. surister commented on Feb 26, 2026

    @surister
    Contributor

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

  7. amotl commented on Feb 28, 2026

    @amotl
    ContributorAuthor

    It looks like this patch can heal CI already.

  8. amotl commented on Mar 1, 2026

    @amotl
    ContributorAuthor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions