Skip to content
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.

Sign up for GitHub

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

Jump to bottom

IIS and PHP 7.4 cause "Bad file descriptor" notice #36413

Closed
no-one opened this issue Apr 10, 2020 · 2 comments
Closed

IIS and PHP 7.4 cause "Bad file descriptor" notice #36413

no-one opened this issue Apr 10, 2020 · 2 comments
Labels
Bug HttpKernel Status: Needs Review

Comments

@no-one
Copy link

no-one commented Apr 10, 2020 •
edited

Symfony version(s) affected: 4.4.7

Description
In the mentioned constellation (IIS + PHP 7.4) Symfony generates a "Bad file descriptor" notice. This is also documented here: https://bugs.php.net/bug.php?id=79166 and is created in the Logger.php in line 82.
Even though this was already mentioned on bugs.php.net, I wanted to report it here as well, because Symfony is currently not usable with this webserver and PHP 7.4.

How to reproduce
Run Symfony 4.4 with IIS and PHP 7.4 with APP_ENV=dev
@no-one no-one added the Bug label Apr 10, 2020
@xabbuh xabbuh mentioned this issue Apr 12, 2020
Merged
@xabbuh
Copy link
Member

xabbuh commented Apr 12, 2020

Can you confirm that #36434 will fix this?

fabpot added a commit that referenced this issue Apr 12, 2020
@fabpot
bug #36434 [HttpKernel] silence E_NOTICE triggered since PHP 7.4 (xab…
4e6a3bd 
…buh)

This PR was merged into the 3.4 branch.

Discussion
----------

[HttpKernel] silence E_NOTICE triggered since PHP 7.4

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix #36413
| License       | MIT
| Doc PR        |

Commits
-------

c4e2c44 silence E_NOTICE triggered since PHP 7.4
@fabpot fabpot closed this as completed Apr 12, 2020
@no-one
Copy link
Author

no-one commented Apr 12, 2020

Can you confirm that #36434 will fix this?

Yes, that's how I fixed it locally for me. I was just unsure if that was also "officially" the right solution. Thanks @xabbuh

@no-one no-one mentioned this issue Jul 3, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug HttpKernel Status: Needs Review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@fabpot @no-one @xabbuh @carsonbot