Composer job always fails in CI pipeline

Created on 3 February 2025, 6 months ago

Problem/Motivation

Trying to create an MR to fix any issue results in tests failing during the "composer" step.

ERROR: Uploading artifacts as "archive" to coordinator... 413 Request Entity Too Large  id=4229178 responseStatus=413 Request Entity Too Large status=413 token=glcbt-64
FATAL: too large                                   
Cleaning up project directory and file based variables
00:00
ERROR: Job failed: command terminated with exit code 1

Steps to reproduce

Run the pipeline.

See https://git.drupalcode.org/issue/pdf_api-3500294/-/jobs/4229190

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Version

2.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States byrond

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @byrond
  • πŸ‡ΊπŸ‡ΈUnited States byrond

    This is currently blocking any issue with an MR, and specifically πŸ› Config schema for chroot does not match usage Active . That, in turn is blocking πŸ› Dependency version constraint block Drupal 11 upgrade Active , which is needed to actually allow the Printable module to install on a Drupal 11 site.

    Could someone with access to the project GitLab please take a look and resolve the issue to allow the two (extremely simple) referenced MRs to be reviewed, making Printable actually D11-compatible?

  • πŸ‡¦πŸ‡ΊAustralia nigelcunningham Geelong

    Thanks for bringing this to my attention - not sure why I haven't seen the related issues. I'll pause the work I'm doing on another module and get this sorted.

    Nij

  • πŸ‡¦πŸ‡ΊAustralia nigelcunningham Geelong

    Ok; I think I've gotten the artifact issue sorted - I needed to copy in the contents of one of the template files and manually insert extra excludes for the fonts that the vendor libraries bring in. Hopefully the maintainers of the gitlab scripts will eventually include support for overriding or extending the excludes and that will no longer be needed. For now though, it's at least getting further than it was and will hopefully successfully run everything.

    Now that I'm aware of the other issues, I'll babysit their pipelines for a bit and hopefully even merge the PRs today.

    Thanks again for bringing this to my attention!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024