-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[VarDumper] [bugfix] Make possible to create sync tcp-connection #47419
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 |
Is this change enough? Asking because the CI job on AppVeyor is still failing. |
It says Can't see how it's connected to my changes. |
@xabbuh the failure is not related to this change (this is the server process failing to start for whatever reasons.) @nikserg what about just always going in non-async mode? I don't like adding an option for something that is supposed to work out of the box. As far as I tested correctly locally, this would provide the same DX. /cc @ogizanagi WDYT? Side note: this is for 5.4 |
Could someone test on Windows please? |
I fully agree 👍🏻 |
@nikserg : Let's always go in non-async mode? |
Closing as this stalled, please resubmit if anyone is up to do the last steps. |
This PR was merged into the 5.4 branch. Discussion ---------- [VarDumper] Make the server TCP connection sync | Q | A | ------------- | --- | Branch? | 5.4 <!-- see below --> | Bug fix? | yes | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tickets | Fix #46145 <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead --> | License | MIT | Doc PR | N/A Alternative to #47419, since the async mode is not consistently working and I agree with Nicolas [about not adding a new option](#47419 (comment)) to control this. Let's always go non-async. Commits ------- 7580ada [VarDumper] Make the server TCP connection sync
On some systems creating async TCP connection results in "failed to open stream: Resource temporarily unavailable" exception. To solve this, added
VAR_DUMPER_ASYNC
variable, which is true by default, so won't affect default behavior.If one faces "failed to open stream: Resource temporarily unavailable" error, he should add
VAR_DUMPER_ASYNC=0
to.env
file, and problem would be solved.