Buff info gets stuck if the unit goes out of range

[nebularg]

I was testing enemy buffs using a rare mob and would leash it to reset. Sometimes it would get out of combat log range before the removed event fired so the buff would stay shown until it was applied again.

With the short combat log range now, you might want to be a bit more aggressive with removing expired buffs/invalidating the cache. Kind of an edge case, but it could be annoying.

[gobacktogo]

(i hope the following is related in a significant enough way that it warrants my posting here instead of creating a new issue. if i was to create a separate issue i would chose the exact same title)

buff info also seems to get stuck on friendly buffs. i keep hearing "rebuff motw pls" in raids, while my unit frames (elvui, presumably using libclassicdurations for buff durations) show the buff at almost completely full duration. when i ask them how much time is actually left on their active motw they, its always seconds or maybe 1-2 minutes. pretty sure this is a rather recent issue, i think the OP is right that it might be related to the combat log distance change.

[DDCorkum]

I did some testing and found that LibClassicDurations works pretty reliably as a simple wrapper whenever source == "player" because then you know you were in range when the ability was initially cast.

Whenever source ~= "player" I stop using the return value from LibClassicDurations because it can produce inconsistent results if someone refreshes a buff that I had previously applied while I'm now out of range.