id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
244	infinite incident loop when logging non-serializable event values	Brian Warner		"A recent change to Twisted caused the loglevels passed into twisted.python.log.msg() to use special `NamedConstant` objects instead of simple integers. When Foolscap is configured to bridge twisted logs into foolscap, it attempts to serialize these objects, which fails, which provokes another error, which fails, etc.

The consequence is that any error causes the process to go into an infinite loop and spam the logging system forever. If it is configured to write incidents to a directory, this will also eventually fill up the disk.

I think we need to translate these constants into the old-style integers in the bridge function.
"	defect	closed	critical	0.10.0	logging	0.9.1	fixed