Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.1.14

Bug #20485 PHP Notice: Uninitialized string offset: -1 in Net/SmartIRC.php on line 1683
Submitted: 2015-01-14 21:45 UTC
From: skaos Assigned: garrettw
Status: Closed Package: Net_SmartIRC (version 1.1.5)
PHP Version: 5.4.36 OS: Debian
Roadmaps: (Not assigned)    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 15 + 31 = ?

 [2015-01-14 21:45 UTC] skaos (Denny Bortfeldt)
Description: ------------ Everytime i want to connect to a server, the script print out more than 20k lines in 1 sec after the client connected in a channel. The client privmsg in a channel and then this offset-errors occurs. I don't know how this happen, because normaly the while-do-loop should only entered when there is something to stream.


 [2015-01-14 22:20 UTC] skaos (Denny Bortfeldt)
-Summary: PHP Notice: Uninitialized string offset: -1 in /var/www/clients/client1/web31/ +Summary: PHP Notice: Uninitialized string offset: -1 in Net/SmartIRC.php on line 1683
 [2015-01-15 03:09 UTC] garrettw (Garrett Whitehorn)
I'm not sure either, but I'll see if I can figure it out. I would say to try downloading the latest code from Github, but I doubt it will make any difference. Still, if you want to try it, feel free.
 [2015-01-15 04:00 UTC] garrettw (Garrett Whitehorn)
I just made a new commit on Github. Could you download the latest code from there and see if that fixed it?
 [2015-01-15 04:15 UTC] skaos (Denny Bortfeldt)
Nice! You're awesome. Everything works perfekt now. Thank you very much for this bugfix and your nice project work!
 [2015-01-15 04:27 UTC] garrettw (Garrett Whitehorn)
-Status: Open +Status: Closed -Assigned To: +Assigned To: garrettw
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Thanks for your kind thoughts! I don't know why that even fixed it. Doesn't make sense, really, but oh well.