Skip to content

Fix GitLab API pagination - #7402

Draft
gavinelder wants to merge 1 commit into
docs/gitlab-tree-pagination-adrfrom
feature/gitlab-linked-pagination
Draft

Fix GitLab API pagination#7402
gavinelder wants to merge 1 commit into
docs/gitlab-tree-pagination-adrfrom
feature/gitlab-linked-pagination

Conversation

@gavinelder

@gavinelder gavinelder commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • expose checked HTTP responses to repository providers so pagination headers are available
  • follow GitLab-provided rel="next" links for branch and tag listings
  • request GitLab’s maximum page size and reject unsafe or cyclic continuation links

Test plan

  • ./gradlew :nextflow:test --tests nextflow.scm.RepositoryProviderTest --tests nextflow.scm.GitlabRepositoryProviderTest --rerun-tasks

Implementation note

The GitLab override does not retain the base helper’s @Memoized inner call. In practice, branch and tag listings are called once per provider instance, and memoizing a method whose key includes a Closure argument provides little useful reuse. Keeping pagination state local also avoids caching response-header traversal.

Stack

Signed-off-by: Gavin Elder <gavin.elder@seqera.io>
@gavinelder
gavinelder force-pushed the feature/gitlab-linked-pagination branch from 084fdc3 to 8be74d0 Compare July 28, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants