Bug #74556 [Com]: stream_socket_get_name returns \0 string instead of false

Edit report at https://bugs.php.net/bug.php?id=74556&edit=1 ID: 74556 Comment by: cpuidle at gmx dot de Reported by: cpuidle at gmx dot de Summary: stream_socket_get_name returns \0 string instead of false Status: Closed Type: Bug Package: Streams related Operating System: OSX PHP Version: 7.1.4 Assigned To: pollita Block user comment: N Private report: N New Comment: Mhm. The bug is in the changelog for 7.1.7 but I'm still seeing it (or something similar) in 7.1.8. It has actually gotten worse (test case from this issue): /Users/Documents/htdocs/vz/sock.php:8: bool(false) /Users/Documents/htdocs/vz/sock.php:8: string(15) "\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000" Instead of string(1) there's now a string(15) returned. @Harald: I'll discontinue the side discussion with you. Previous Comments: ------------------------------------------------------------------------ [2017-10-07 10:55:17] spam2 at rhsoft dot net "disappointed with the culture" when the fix was commited to 20 days after the report and within nearly 5 months you are NOT willing to read the existing comments or even update php where you would have seen it fixed and in the NEWS file *is rude* ------------------------------------------------------------------------ [2017-10-07 10:49:14] cpuidle at gmx dot de > It was closed because it was fixed. And there *was* a comment for that - it was automatic so > sorry if you wanted something more personal. Great. My mistake I didn't notice that- had expected it in the "changes" section, sorry for the confusion. > What is your problem? There was a bugfix commited including a changelog entry pointing to this > Bugreport - so what about you are whining? I think that's the exact tone that doesn't attract people. If you read my comment you'll notice it wasn't rude... ------------------------------------------------------------------------ [2017-10-07 10:42:06] spam2 at rhsoft dot net What is your problem? There was a bugfix commited including a changelog entry pointing to this Bugreport - so what about you are whining? ------------------------------------------------------------------------ [2017-10-07 10:38:37] requinix@php.net It was closed because it was fixed. And there *was* a comment for that - it was automatic so sorry if you wanted something more personal. ------------------------------------------------------------------------ [2017-10-07 10:28:29] cpuidle at gmx dot de @pollita@php.net would you kindly explain why this bug has been closed without any comment? I've tried to provide every analysis I could including PHP sources. Doesn't that at least deserve a small token of appreciation like an answer? Disappointed with the culture :( ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=74556 -- Edit this bug report at https://bugs.php.net/bug.php?id=74556&edit=1