New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecation notice printed to stdout on PHP 8.1 [Composer 1.10.23] #10345
Comments
I believe these occur without formatting because they are happening at parsing time and our error handler isn't registered yet.. maybe? Anyway AFAIK it's fixed in 2.x so should be able to backport, although I was hoping I wouldn't have to do that ;) |
So is the |
Yeah there's a gap here between error_reporting set and registering the error handler.. not sure exactly why it'd already load HelperSet nor ArrayRepository before ErrorHandler is registered though Lines 16 to 70 in 0dbc736
Oh but I see, that's from main branch. 1.10 does it later, that explains things: composer/src/Composer/Console/Application.php Line 130 in b8e5b1d
|
if you want to send a PR to 1.10 moving error handler registration to match main branch + also backport the changes in ErrorHandler itself to ignore the 8.1 stuff that'd be great. composer/src/Composer/Util/ErrorHandler.php Lines 58 to 63 in e7683e2
Probably should apply the |
okay I'll have a look ASAP; hope I can fix this tonight still (it's blocking my ability to roll out 8.1 on Heroku at the moment, so it's easy to justify :)) |
Don't expect a release until tomorrow tho, but if you can PR by then it increases the chances it gets resolved tomorrow that's for sure :) |
PR in #10346! |
I know the branch is more or less EOL, but... for people running Composer 1 projects, it's still necessary to install them using Composer 1 if there are plugins involved, so...
This obviously breaks programmatic use cases where e.g. the Composer version, config, whatever, is determined by code.
Running without
2>/dev/null
shows that that deprecation notice is different from the others that get printed (which are also ANSI colored); is this a sub-process or something?The text was updated successfully, but these errors were encountered: