Bug #74556 [ReO->Csd]: 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 Updated by: pollita@php.net Reported by: cpuidle at gmx dot de Summary: stream_socket_get_name returns \0 string instead of false -Status: Re-Opened +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: 3v4l disagrees with you: https://3v4l.org/VStV6 Previous Comments: ------------------------------------------------------------------------ [2017-10-07 13:26:45] kelunik@php.net Re-opening, as behavior got worse. ------------------------------------------------------------------------ [2017-10-07 13:25:57] kelunik@php.net @rhsoft: Please stop with your tone. cpuidle simply missed a comment, which is probably caused by bugs.php.net's sub-optimal interface. It's nothing about willingness or something like that, it simply got missed. ------------------------------------------------------------------------ [2017-10-07 12:54:36] cpuidle at gmx dot de 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. ------------------------------------------------------------------------ [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... ------------------------------------------------------------------------ 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