5 Commits (afa0100e271be3b049e2cfe3bfe68bbb764a6ef2)

Author	SHA1	Message	Date
Dan Mace	0ad8342a55	Log ErrUnexpectedEOF from watches as warnings ... Watches are often established via long-running HTTP GET requests which will inevitably time out during the normal course of operations. When the watches time out, an io.EOF or an io.ErrUnexpectedEOF will bubble up to client components such as StreamWatcher and Reflector. Treat EOF as a clean watch termination. Treat ErrUnexpectedEOF as a less-clean but non-fatal watch termination and log the event at the warning level. This greatly reduces the amount of log noise generated during what is ultimately normal operation, and adds the flexibility for the operator to make a distinction between the EOF conditions if so desired (by adjusting the logging level).	2014-12-05 15:03:07 -05:00
Clayton Coleman	6778a8d88d	watch/iowatcher should log non EOF errors encountered	2014-09-22 16:03:07 -04:00
Daniel Smith	0d30a656ef	Do interface{} -> runtime.Object rename everywhere	2014-09-07 22:19:24 -07:00
Vojtech Vitek (V-Teq)	59f58cd043	Unify Godoc formatting, fix various typos ... Signed-off-by: Vojtech Vitek (V-Teq) <vvitek@redhat.com>	2014-09-02 13:41:03 +02:00
Daniel Smith	91375f4c04	Split httpWatcher into watch.StreamWatcher and tools.APIEventDecoder.	2014-07-21 16:07:58 -07:00