-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Process] argv array in env resulting in "Array to string conversion" error #44197
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
Comments
Can you please provide a reproduder for this? I fail to see how this can happen. |
I'm also facing this issue.
|
Thank you all but there is no question whether some of you experience this or not. |
Ok, I dumped the $env array in the loop. and it seems this is the item which fails: |
At which line did you dump this please? |
Yes, sorry:
|
OK thanks. Can you please try dumping as I suggested in #44197 (comment)? |
Can you please try #44208? |
Yes, that fixed it 🎉. Just FYI: both items |
… (nicolas-grekas) This PR was merged into the 4.4 branch. Discussion ---------- [Process] exclude argv/argc from possible default env vars | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #44197 | License | MIT | Doc PR | - For some reason `getenv()` can contain these special keys. Looks a lot like #7196 Commits ------- 36d254a [Process] exclude argv/argc from possible default env vars
Thanks for the help debugging this! |
Notice: Array to string conversion coming on before response from the version 4.4 |
Notice: Array to string conversion
in app:users:checkpassword since last release
systemli/userli#341
Symfony version(s) affected
5.3.11
Description
After upgrading the process component from 5.3.7 to 5.3.11 I sometimes get the following error:
Notice: Array to string conversion
on https://github.com/symfony/symfony/blob/5.4/src/Symfony/Component/Process/Process.php#L344A simple
dump($k, $v)
showed"argv"
and[]
.How to reproduce
not sure (yet) but version 5.3.11 required.
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: