| 09:19.37 | *** join/#infobot FactBot (n=factbot@pdpc/supporter/sustaining/troubled) |
| 09:19.37 | *** mode/#infobot [+o FactBot] by ChanServ |
| 12:11.54 | troubled | simonrvn: hmmm |
| 12:12.15 | troubled | regarding the we have a NULL chan warning... |
| 12:12.39 | troubled | UserExtra.pl seems to consider a blank channel as meaning all channels |
| 12:13.06 | troubled | yes the Scheduler.pl seems to think it is a no no, and should be deleted (although they actually forget to do it) |
| 15:41.09 | *** join/#infobot TimRiker (n=timr@216.49.181.128) |
| 15:41.09 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 15:44.15 | troubled | TimRiker: hey, question |
| 15:44.41 | troubled | "we have a NULL chan in hash channels? removing" in Scheduler.pl |
| 15:44.54 | troubled | for one, it doesnt actually get removed |
| 15:45.19 | troubled | two, UserExtra.pl seems to think a null has is used to imply "all" channels. |
| 15:46.18 | troubled | i can toss in the code to actually delete it, but it seems to only get a null channel if I say something in the channel the bots in, and then only after about ~16 minutes on a fresh start do I start getting the null chan |
| 15:47.26 | troubled | hard to tell which file might have a null $chan that sets it, although im leaning towards UserExtra.pl atm. any ideas? I would have to remove something that is required for the bot to function. |
| 18:13.41 | TimRiker | no idea. I meant to track that down, but never did. experiment. :/ |
| 18:14.15 | TimRiker | _default likely got added after that I would think. |
| 18:14.25 | troubled | well, i was hoping to get your approval before i added/removed stuff |
| 18:14.33 | TimRiker | not sure that we need an ALL if we have a _default |
| 18:14.46 | troubled | first of all, it seems to go fine forever, _until_ i say something in a channel |
| 18:14.49 | TimRiker | knock yerself out. just test it first. :) |
| 18:14.54 | troubled | shortly after, one of the scheulers triggers it |
| 18:15.12 | troubled | then the code that says "removing!" does nothing |
| 18:15.37 | troubled | it just has a sub if that says if its a null then say "we shouldnt be here" |
| 18:16.12 | troubled | for starters, im gonna add the code to actually drop the null channel hash, until i can track down what file is setting it |
| 18:17.11 | troubled | i did do a for lcv in `grep .....` for all the instances of "%channel" in the src dir. ive see all the files and places where it could happen, but i really gotta add about 20 or 30 debug lines to catch which $chan might be null. |
| 18:17.45 | troubled | shouldnt be hard to track down, until i noticed that one of the files seems to expect a null channel |
| 18:18.29 | troubled | seems like at some point, someone made the decision that a null channel passed to @_ is to be treated as all channels. im assuming that it gets set in there. |
| 21:29.50 | *** join/#infobot TimRiker (n=timr@216.49.181.128) |
| 21:29.51 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:31.43 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:31.43 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:34.05 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:34.05 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:39.44 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:39.44 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:41.12 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:41.13 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:45.07 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:45.08 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:46.26 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:46.27 | *** mode/#infobot [+o TimRiker] by ChanServ |
| 21:56.22 | *** join/#infobot TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 21:56.23 | *** mode/#infobot [+o TimRiker] by ChanServ |