Forum Replies Created
-
AuthorPosts
-
Lukas Kaisers
ParticipantHello 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.
Lukas Kaisers
ParticipantI'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.
Lukas Kaisers
ParticipantHi,
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.jsoncould return415 Unsupported Media Type
* the same endpoint also returned302 Foundin other cases
* when explicitly sendingAccept: application/json, the request returned302 Foundconsistently in our CI testsBecause 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
Lukas Kaisers
ParticipantUnfortunately, I have to take back my last message. The installation failed again. What does the HTTP status 415 mean?
Lukas Kaisers
ParticipantHello 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?
August 23, 2024 at 1:38 PM in reply to: Access previous versions of Meta Box AIO via Composer #46217Lukas Kaisers
ParticipantThank 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.
-
AuthorPosts