﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
190	log gatherer fails to process more incidents when processing a given incident fails (e.g. due to serialization problems)	davidsarah	Brian Warner	"LAE has its Tahoe storage servers configured with a log gatherer. Some of the incidents being sent by servers included unserializable objects (due to a bug in the Tahoe S3 backend which has been fixed). This caused the 'latest' file maintained by the log gatherer for each affected storage server to be stuck at or just before (the latter, I think) the unserializable incident, so subsequent incidents on that server were not requested, even though they had no serialization problem. IRC discussion:

{{{
(01:22:16) davidsarah: (01:20:23) zooko: There was an instance of TahoeS3Error that foolscap was asked to serialize.
(01:22:16) davidsarah: (01:20:35) zooko: And it raised a Violation exception saying ""cannot serialize"".
(01:22:44) davidsarah: it's the causing subsequent incidents not to be sent that is confusing
(01:22:55) zooko: Yes, being able to withhold write-access while granting read-access is frequently nice.
(01:23:05) zooko: davidsarah: I posted a link to the foolscap github...
(01:23:17) zooko: https://github.com/warner/foolscap/blob/3fd4331b67abf307aa38e898e7d1e7fd37fc0b3d/foolscap/logging/gatherer.py#L343
(01:23:26) ***davidsarah looks
(01:23:27) zooko: So, that violation exception is happening on the incident reporter side -- the tahoe-lafs storage server.
(01:23:47) zooko: But, over on the incident *gatherer* side, it attempted to fetch the incident, and got instead a message from foolscap saying something like ""Error -- couldn't send you the thing you wanted""
(01:23:54) zooko: and the errback for that doesn't proceed to try the next one.
(01:23:58) zooko: I think. Am I right?
(01:24:08) ***davidsarah looks at the code
(01:25:18) davidsarah: I see, so _got_incident doesn't get called and doesn't recurse to maybe_fetch_incident
}}}"	defect	closed	major	0.6.4	logging	0.6.1	fixed	incident	davidsarah
