codec/codecutils/lex.go: NOOP buffer timeouts during normal operation
Issue #383
new
There’s an issue with how the buffer for the NOOP lexer works, that is, timeouts are triggered under certain conditions in normal operation. If the revid pipeline is started before data is sent to the input of the pipeline, occasionally this period is longer than the timeouts and an error is returned. We either need to rethink these timeouts, or handle the error better so that it doesn’t break the entire pipeline when we actually do want to send data.