I think this was effectively resolved by D12773, since using conduit.token should evade the session timeout.

Per discussion T11508, I'm just going to officially call this a "feature".

I've located the mainframe and uploaded the downloads

phabot is basically on it's way out (T6875), so you might not get much traction with any change to it.

I think there are two issues here:

We don't see this on this install:

In lieu of waiting for a fix to the official phabot, if you're feeling adventurous, I wrote a Phabricator plugin for my open-source IRC bot. My team uses it 24/7 and it meets our needs.

@epriestley, do you have any suggestions on how we might work around this or fix it? The fact that we no longer have a working IRC bot is really painful for us. We don't have any php devs but if you were to pointed us in the right direction I'm sure we could make it work.

@filterfish, @staticshock's patch works fine for me on a 64bit machine.

@staticshock. Yeah, fair enough. I'm running phabricator on a 64bit machine so that'll explain why your patch made no difference. It looks like I'll have to dig a bit deeper!

@filterfish, I'm using that patch as-is on an x86 system, and it works for me. I suspect that the real solution is not to run phabricator on systems that the core team doesn't test on, so we're planning to move our install to x64 in the near future.

@staticshock, did you work out what the underlying problem was? I tried you patch but it didn't make any difference.

In T7829#116214, @epriestley wrote:

• We should move to giving the bot a list of channels to join, and a list of handlers to run in each channel -- not a list of handlers to run at top level, and then other top-level config for each handler about channel behaviors. This also resolves issues like T7800.

Short of an overhaul that won't be available "for a long time", here are the minimal local changes one could make to get notifications working:

I've added more details at T8503

Here's what it looked like in the apache logs: