@hichris123 Because that catches errors after they make it out of the loop, and never restarts the loop. It goes straight to an abort.

This should restart the websocket on error

@Undo Then why not put it after the while true?

Because then the loop will already be done (errored out) and it'll go straight to posting the abort message

By handling the error inside the loop, I hope to avoid an abort.

recovered, but still: Traceback (most recent call last):
  File "ws.py", line 374, in <module>
    a=ws.recv()
  File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 654, in recv
    opcode, data = self.recv_data()
  File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 669, in recv_data
    frame = self.recv_frame()
  File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 744, in recv_frame
    frame_buffer.recv_header(self._recv_strict)
  File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 255, in recv_header

And it's working, apparently

@Undo No, like this: gist.github.com/hichris1234/194b88c30bd33d3277cc

oh, yeah that would work

And it's cleaner

yeah

Want me to commit it, @Undo?

Go for it

Here goes..

[ SmokeDetector ] SmokeDetector started at rev f335151 (Undo1: Merge branch 'master' of github.com/Charcoal-SE/SmokeDetector) (owned by Undo)

oops, accidently killed it

But it looks like it works, thanks @hichris123

[ SmokeDetector ] SmokeDetector started at rev f335151 (Undo1: Merge branch 'master' of github.com/Charcoal-SE/SmokeDetector) (owned by Undo)

@Undo np. :)

:D

Okay, I've got to go. Added Jason to the command whitelist, too.

cya

@Undo github.com/Charcoal-SE/SmokeDetector/commit/…

!!/alive?

!!/status

!!/helloAreYouThere?

!!/alive?

@Undo SmokeDetector ran out of batteries

huh..

!!/status

Uh... might have found what's wrong with Smokey.

oh yeah?

did you break something? ;P

We need a Charcoal Wheel of Blame :D

No, gimme a sec.

Bingo. Not my fault. It's SE's.

@ManishEarth ChatExchange is broken.

Ty

global-fallback 404s

@hichris123 why 404?

O.o

!!/alive?

@hichris123 and @ManishEarth, I restarted Zephyr again this morning (about an hour ago) and it logged in fine. It utilizes this same block of code to jump into 9 different chat rooms across all three chat domains. I can't replicate the error that is posted above.

hm

!!/alive?

Bot started.

>>alive

@ProgramFOX Yes, I'm alive.

>>stop

@ProgramFOX Bot terminated.

lol

@hichris123 and @ManishEarth See the above messages. Looks like ChatExchange works fine. Perhaps @Undo restarted his server but forgot to restart SmokeDetector.

we need him to @Undo the damage.

eh?

I don't remember restarting it...

oh

!!/alive?

That doesn't change that it's dead as of a few hours ago

!!/alive?

@Undo Of course

I... didn't do anything

huh?

!!/status

@ProgramFOX Running since 16:36:30 UTC

aha

Apparently it revived itself just by me opening the screen window it was in

huh, okay

So that's apparently a thing

@Seth Is this a known thing, opening a screen session suddenly revives the stuff running it it?

@Undo sometiems dead screen sessions aren't that dead ;p

@Undo yes? Depends on what you mean by "opening" I guess.. (I use the byobu front end to screen and rarely disconnect so not too experienced here :P)

@SmokeDetector fpu

@ProgramFOX Registered as false positive, added title to Bayesian doctype 'good', whitelisted user.

... That might be the first false-positive "baba" has given us.

Could cause an issue if our spammers move from ELU to Hinduism.

Presumably a phone number will still register as bad, even though a word is actively whitelisted?

@Undo blacklist Hinduism?

for the baba one

"Baba" means saint, sort of

hmmm

I dunno

We haven't really had a problem with FPs from that site on 'baba' yet, have we?

@Undo we have other keywords hat catch it

@ProgramFOX That's... super weird.

Also, @Undo you need to pull a new rev.

Yep, now it's working @ProgramFOX. Maybe someone broke something for a few hours/minutes?

!!/alive?

@Doorknob Of course