-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Process] Fix Process::getEnv() when setEnv() hasn't been called before #45931
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
Conversation
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
I think it might be better to initialize the property to the empty array, then we wouldn't have to patch this method.
Also, since this is a bugfix, it should target 4.4, and should have a test case. Can you add one please? (I can handle the re-targeting while merging)
Sorry I have heavy work on my job, so I'm afraid that I'm not available to do future works. Just fix it thought your standard way, thanks. |
Thanks @asika32764. |
AS
getEnv()
return type is array, if aProcess
object has no default env and is NULL value, callinggetEnv()
will get error.