WowAce

What steps will reproduce the problem?
1. Join AV
2.
3.

What is the expected output? What do you see instead?
BugSack registered the error below

What version of the product are you using?
r301

Do you have an error log of what happened?
57x Grid2-3.3.0.301\GridRoster.lua:172: assertion failed!
Grid2-3.3.0.301\GridRoster.lua:172: in function `?'
CallbackHandler-1.0-5 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[2]":4: in function <[string "safecall Dispatcher[2]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[2]":13: in function `?'
CallbackHandler-1.0-5 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

Please provide any additional information below.

Started right after I zoned into AV. Seemed to be tied to join/leave messages, but I'm not 100% on that.

Just did a closer look - pets seem to trigger more than players... odd.

Fixed in rev303.

nope:

1x Grid2-3.3.0.303\GridRoster.lua:173 assertion failed!
Grid2-3.3.0.303\GridRoster.lua:173 in function `?'
CallbackHandler-1.0-5 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
<string>:"safecall Dispatcher[2]":4: in function <[string "safecall Dispatcher[2]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[2]":13: in function `?'
CallbackHandler-1.0-5 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119

  ---

Just got that, too.... but my game locked shortly thereafter and I was unable to get the trace. It happened right after a graveyard rez.

Fixed in r305.