simple_away not setting away on lastclientdisconnect about znc HOT 5 CLOSED

Huh.
No, it's not just you...
simple_away seems to be loaded as user module for you, and when the timer fires, there's no m_pNetwork anymore.

It can be fixed in simple_away... But I suspect that many similar bugs are in many different places.
We really should do something about the way how to determine current user/network from different stuff like timers and sockets...

from znc.

I cleaned up my original message a bit. It seemed confusing in some parts.

Thanks for the reply. I realize you've pretty much just overhauled the network code as I just finished fixing an external module (notifo-push) to work with m_pNetwork in .203. So I understand it's no where near complete. It's just more fun to stay on bleeding edge than stable :-)

Great work overall.

from znc.

I did want to add that the module autoreply works perfectly. Which is also a user module.

I'm wondering if the function handle could be converted to work with simple_away. I will have to try this and see.

from znc.

I have fixed another bug in this module where you will not become away if you are attached from another network. I made this module a network module in the same patch so it will fix the issue you are having.

As @DarthGandalf says, I think we should still explore the idea of another solution so user modules can use a CIRCNetwork.

from znc.

Whoooo! Thanks Kyle! It works again

from znc.