Support Forum ยป User Profile

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Installation via Composer fails #49911
    Lukas KaisersLukas Kaisers
    Participant

    Hello Peter,

    the composer file roughly looks like this (simplified example file).
    The GitHub workflow is nothing special, I'm using the "ubuntu-latest" runner (nothing self-hosted), the shivammathur/setup-php@v2 action to install PHP (currently with version 8.4) and then I'm calling composer install (without a lockfile because I want to download the latest version).

    The workflow just completed successfully, the problem is that I can't reproduce the issue. Sometimes it works, sometimes not. When it doesn't, I'm getting the error code that I've posted at the top of this thread.

    in reply to: Installation via Composer fails #49901
    Lukas KaisersLukas Kaisers
    Participant

    I'm probably giving up on this and start to version Meta Box AIO myself again via a private GitHub repo. Even with the explicit Accept header I had failing installations.

    in reply to: Installation via Composer fails #49900
    Lukas KaisersLukas Kaisers
    Participant

    Hi,

    I wanted to provide a short update.

    At the moment, the installation is working again without any change on our side, and we are not able to reproduce the issue consistently in a local environment.

    However, we were able to reproduce the problem in GitHub Actions with raw curl requests to the Composer endpoint.

    In GitHub Actions we observed:

    * requests to https://packages.metabox.io/<KEY>/packages.json could return 415 Unsupported Media Type
    * the same endpoint also returned 302 Found in other cases
    * when explicitly sending Accept: application/json, the request returned 302 Found consistently in our CI tests

    Because the behavior is not consistent across environments and can change without configuration changes on our side, this looks like an environment-dependent issue, possibly related to proxy/CDN/WAF handling or request classification.

    So while the issue is currently no longer occurring for us, we believe there is still an underlying instability in how requests to the package endpoint are handled in CI environments.

    Please let us know if you would like the curl logs from the GitHub Actions runs where the endpoint returned 415.

    Best regards

    in reply to: Installation via Composer fails #49899
    Lukas KaisersLukas Kaisers
    Participant

    Unfortunately, I have to take back my last message. The installation failed again. What does the HTTP status 415 mean?

    in reply to: Installation via Composer fails #49898
    Lukas KaisersLukas Kaisers
    Participant

    Hello Peter,

    except of the "extra" and "autoload" properties everything is the same in my composer file. I should have mentioned that the error only occurred in my CI pipeline (GitHub actions) and not locally. Today somehow the installation succeeded again. Did you change anything?

    in reply to: Access previous versions of Meta Box AIO via Composer #46217
    Lukas KaisersLukas Kaisers
    Participant

    Thank you very much, otherwise there's no chance we can save our theme settings because of the validation bug of cloneable fields that are required.

Viewing 6 posts - 1 through 6 (of 6 total)