egghelp/eggheads community

queue problem

2002-02-09T18:59:00-04:00

perhaps a -nostack flag is needed for putserv/putquick/puthelp

Statistics: Posted by Petersen — Sat Feb 09, 2002 6:59 pm

queue problem

2002-02-09T18:22:00-04:00

Hm... I heard about the problem but was never given really good evidence as to why it was happening. Thank you for doing so. From looking at this, I think it is also caused by stacking (which is completely normal) and should be fixed somehow.

Jeff

Statistics: Posted by guppy — Sat Feb 09, 2002 6:22 pm

queue problem

2002-02-09T06:24:00-04:00

The 'stacked messages' suggestion seems to be the most feasible explanation. If that's the case, perhaps somebody could explain why it is present.

I believe that having messages sent in this way is inappropriate for NOTICE, and probably just as much so for PRIVMSG. I didn't find anything in the newest version of the conf file that mentioned it, so I'll assume it's a compulsory feature. Is it really neccessary?

- Tom

Statistics: Posted by ClubCX — Sat Feb 09, 2002 6:24 am

queue problem

2002-01-30T12:37:00-04:00

lag would not cause messages to appear in reverse order. reroutes might, but the chances of one happening every time this command is used is stupidly small.

Statistics: Posted by Petersen — Wed Jan 30, 2002 12:37 pm

queue problem

2002-01-30T12:12:00-04:00

Did anyone think about lag?

Statistics: Posted by Yourname — Wed Jan 30, 2002 12:12 pm

queue problem

2002-01-30T08:23:00-04:00

without testing this myself, here is my theory.

my guess is that the bot is taking advantage of stacked messages, ie PRIVMSG nick1,nick2,nick3,nick4,nickN :message

Thus, lets say you have 5 lines to send to the ppl, which are A, B, C, D and E. This is what could be happening

!trigger
PRIVMSG nick1 :A
PRIVMSG nick1 :B
!trigger
PRIVMSG nick1,nick2 :C
PRIVMSG nick1,nick2
PRIVMSG nick1,nick2 :E
PRIVMSG nick2 :A
PRIVMSG nick2 :B

you should enable console mode +v to see if this is really what is happening.

Statistics: Posted by Petersen — Wed Jan 30, 2002 8:23 am

queue problem

2002-01-30T01:40:00-04:00

I've encountered a problem using the help queue recently. If the bot is already sending data to a user, and then it loads the same data into the queue to be sent to another person, it will send it to the second person in the wrong order.

Basically, it cuts the output at the point between what had already been sent to the first person and what it had left to send to that person, although both users still receive the complete information.

Here's an example. It should be clear where the data *should* have begun and *should* have finished..

[03:16] sb userlist
[03:16] <@ClubCX> It's like an expanded version of handlelist
[03:16] sb userlist
[03:16] <@ClubCX> sb userlist
[03:16] -SiliconBot- Channel Access: ChanOwner
[03:16] -SiliconBot- Known Hosts: *!jewel@*.uk.com
[03:16] -SiliconBot- First Added: 29 Jan 2002 (20:48) Last Seen: 01 Jan 1970 (00:00)
[03:16] -SiliconBot- End of userlist
[03:16] -SiliconBot- #training Userlist
[03:16] -SiliconBot- [1] Handle: ClubCX Global Flags: fhjmnoptxAL

I seem to recall hearing that duplicate messages to the same target were being prevented, but since this is to different targets it should be unaffected. I've only encountered this problem since upgrading to 1.6.8. Has anybody else seen anything like this?

- Tom
http://www.botservice.net

Statistics: Posted by ClubCX — Wed Jan 30, 2002 1:40 am