Growl Notification and Contact Alert Awayness

[spam@weks.net]

I currently have the following set (and no others) on a user:

• Contact returns from away
  • Display a Growl notification
  • Play the sound "..."
• Contact signs on
  • Display a Growl notification
  • Play the shound "..."

When the user sets herself away, I get a Growl notification that she "is back." No.. no, she's not.

[evands]

Should confirm and fix if appropriate for 0.86

[Diatribe]

I have something similar happening, which sounds like the same problem.

1. I get a "returned from idle" right before a contact goes away.

2. I get a "contact came back" right before he signs off or goes away.

I get these events even though they are wrong and I get them independent of the event system used (i.e. Growl, sounds, etc.)

Oh, and it seems that #556 is a dupe of this.

[tick]

.8x is only for security issues now, moving to 1.0

[cbarrett]

This sounds like an issue with the event coalescing. Evan, think you could find a couple minutes to explain that to me again?

[evands]

The OP's description doesn't sound like desired behavior at all -- the away event is being displayed as a returned event. Straight bug... haven't seen it myself. Does it really exist?

Diatribe's bug above sounds like it might be protocol-specific.. for example, if a contact can't be both idle and away and went from idle to away, perhaps idle is being cleared and then away set. The 'contact came back' is from the away status being cleared when the contact signs off... should be suppressed somehow.

And as far as the actual event coalescing which was supposed to be able to suppress a 'contact went away' in favor of the away message if possible... I'm not convinced it works at all, especially with the delay from AIM we have to deal with now ;)

[cbarrett]

There's a delay from AIM? And it's too bad that the coalescing doesn't work; that was a neat feature.

[tick]

Can't duplicate, closing.

[zacw]

(In [23990]) Fix the world's most oddly placed bang, fixing a longstanding issue where the wrong event would fire for a contact. Fixes #468. Fixes #5551.

[zacw]

Nothing like the satisfaction of fixing your own 3 year old ticket.

[zacw]

(In [23997]) Fix the case of a metacontact which was available on connect going away causing the "come back" event to be fired. This would occur when the cache had a nil-entry and an event fires causing the cache to be updated before the meta contact is fully away, which triggers the "came back" event. Refs #468.

[evands]

(In [24152]) Backported [23997]: Fix the case of a metacontact which was available on connect going away causing the "come back" event to be fired. This would occur when the cache had a nil-entry and an event fires causing the cache to be updated before the meta contact is fully away, which triggers the "came back" event. Refs #468.

Backported [23990]: Fix the world's most oddly placed bang, fixing a longstanding issue where the wrong event would fire for a contact. Fixes #468. Fixes #5551.