Bug with the queue

Speeddymon · Post by **Speeddymon** » Fri Nov 14, 2008 11:19 pm

So I've got a bug with queueing now .. i run a census, and try to do a /who .. stop census cause im too impatient, queue never runs, subsequent /who's go into the queue .. have to reload to clear queue

Edit: in case you can't reproduce it, i am using LibWho-2.0 with WIM.. I know its supposed to play nicely, but ya never know..

Post by **Rollie** » Sat Nov 15, 2008 4:05 pm

If you do a /who while a scan is in progress, it will pause automatically, no need to pause it yourself.

At any rate, I'll try to reproduce!

Speeddymon · Post by **Speeddymon** » Sun Nov 16, 2008 3:20 am

It's not doing that. I'm getting the message "/who (whatever) added to queue" and then if I stop the census, it never runs the queue. If I let the census finish, then the queue runs just fine. I do remember that it's supposed to pause the scan, so I think the queue is part of LibWho-2.0 working itself around Census. Let me know what if anything you find, and I'll try to get in touch with the libwho guys..

DM. · Post by **DM.** » Sun Nov 16, 2008 9:39 am

Its a bug, I've had this happening for months now. I don't know what the cause is, but considering I have alot of mods installed I figured one of those is interfering and I just have to spam that /who query over and over until it finally goes through with Census. It doesn't happen all the time, most of the time the /who query goes through fine, just the occasional time where it won't go through unless I try several times.

Yes if you stop the Census the query will not be processed... This happens to me. I kinda expected it since the query is being captured by Census to be processed and doesn't make it to the Blizzard UI to process until Census finds a gap where it can send that /who query, and since you stopped Census your query was lost.

I think its another mod installed that is interfering, but I checked and none of mine use LibWho library, but considering the amount of mods I use I figured one of those could be the problem.

Solution? Just spam that /who query if you don't get a response back within 5 secs after the first one. It might take a few tries but it will usually go through.

Post by **Rollie** » Sun Nov 16, 2008 11:44 am

Huh, I haven't seen this happen and I run with quite a few mods myself =)

Stadler · Post by **Stadler** » Thu Dec 04, 2008 4:51 am

I'm using SpamMeNot and WIM (my only addons that use a WhoLib), which both have switched over to LibWho-2.0. Maybe thats the problem?

Code: Select all

/script if WhoLibByALeX &#91;...&#93; end;

returns false for me

akhtar · Post by **akhtar** » Sat Dec 27, 2008 3:36 pm

I updated wholib today to fix a bug.

I'm interested to know if this still happens?

The only problem I have seen is that Census' who queries run at wholibs highest priority, and starve out the lower priority queries. That and the <3 results spam in the chatframe.

EDIT: I updated it again, and replaced WhoLibs priority queue with a scheduler which will allow processing of all queues even when census is running loads of queries

uigrad · Post by **uigrad** » Mon Jan 05, 2009 4:23 pm

I posted about a month ago about a conflict with WIM 3.0 and census+. I am still having the same problems today. I disable WIM every time I want to run a census now.

The symptom that I've seen is that /who requests from census+ are thrown into a buffer that lags, and census doesn't know the delay in responses. Census sends "/who 61-70", then receives the response from an earlier /who (all the characters are level 75+) and it just goes on. If the response it receives is less than 50, then it doesn't break down the 61-70 bracket any more, and it loses a big chunk of players.

Dromic · Post by **Dromic** » Mon Jan 05, 2009 10:43 pm

uigrad wrote:I posted about a month ago about a conflict with WIM 3.0 and census+. I am still having the same problems today. I disable WIM every time I want to run a census now.

The symptom that I've seen is that /who requests from census+ are thrown into a buffer that lags, and census doesn't know the delay in responses. Census sends "/who 61-70", then receives the response from an earlier /who (all the characters are level 75+) and it just goes on. If the response it receives is less than 50, then it doesn't break down the 61-70 bracket any more, and it loses a big chunk of players.

Looking the WIM addon in curse and people have been having issues with it. Makes you think there is something wrong with how it it interacts with other addons.
________
John Goss Special