@ArtOfCode I was given a red strike on this for fp- metasmoke.erwaysoftware.com/post/29243 it would be good to have some clearer instructions on dealing with self vandalism reporting thanks
@ArtOfCode Can we prevent the escalation of self-vandalism to the tavern? Because the post isn't "deleted" within 5 minutes, and not marked ignore/naa/false it will be broadcasted there
Yeah, I'd need to look at how we do it. It would have to check that (a) it would be caught by few uniques or repeating chars, and (b) that it's not the first revision of the post. The latter, I'm not sure if we have the information for. @sandwich, any idea if we've got it?
The two most recent manually reported questions from Workspace both matched by the title; should have been reported. metasmoke.erwaysoftware.com/reason/1
> Bad keyword in title, bad keyword in username ---------- Title - Position 1-38: @Live.... X-men Apocalypse Full Movie Username - Position 1-38: @Live.... X-men Apocalypse Full Movie
1. [:29893896] <skipped> 2. [:29893892] <processed without return value> 3. [:29893871] <processed without return value> 4. [:29893868] <processed without return value> 5. [:29893843] That message is not a report.
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 8-24: moviesonlinehdq. Body - Position 8-24: moviesonlinehdq.
File "/usr/lib/python2.7/threading.py", line 495, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
2016-05-25 13:27:21.465481 UTC
error: can't start new thread
Traceback (most recent call last):
File "ws.py", line 169, in <module>
t.start()
File "/usr/lib/python2.7/threading.py", line 495, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
error: can't start new thread
2016-05-25 13:27:55.699315 UTC
File "/media/sda2/SmokeDetector/excepthook.py", line 46, in run_with_except_hook
The "dictionary changed size during iteration" at 2016-05-25 14:41:22.672122 UTC (in BodyFetcher.queue) also points to multiple threads doing same thing.
Can it be that the websockets to the question feeds are staying alive? They basicly close only at the moment when a message is send to them (after the timeout is done), and that only happens when something like a up or downvote happens to the Q
Though the difference is immaterial, since the presence of 'owner' key guarantees there'll be a user object there. API wasn't going to pass None for it.
Which ties to threads, which ties to websocket connection. I think I'll try to log everything that websocket sends to see if there's anything odd. But later.
for site, values in self.queue.iteritems():
2016-05-25 15:15:34.960985 UTC
error: can't start new thread
Traceback (most recent call last):
File "ws.py", line 166, in <module>
t.start()
File "/usr/lib/python2.7/threading.py", line 495, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
2016-05-25 15:15:35.736796 UTC
error: can't start new thread
Traceback (most recent call last):
File "ws.py", line 166, in <module>
t.start()
File "/usr/lib/python2.7/threading.py", line 495, in start
I'm trying to dump a list of all active threads including the current stack of each. I can get a list of all threads using threading.enumerate(), but i can't figure out a way to get to the stack from there.
Background: A Zope/Plone app freaks out from time to time, consuming 100% of cpu and nee...
