Parse_log is very screwy, upon closer inspection... well, that's to say that the log is screwy. Anyway, the problem wasn't that we needed to tell it to ignore all of these new spurious websocket errors. We needed to tell it to ignore the "INFO" lines which were bycatch of the websocket errors. The Websocket errors were actually already being ignored. I think. Anyway, third try is the charm, right?
coverage: 94.434%. remained the same
when pulling fba5f1308586a13eb0eefc0aaf50da9c4217f797 on fix-parse-log-correctly
into df01dcb0fc60a59afb647fe5980ca447ce4c251b on main.
Parse_log is very screwy, upon closer inspection... well, that's to say that the log is screwy. Anyway, the problem wasn't that we needed to tell it to ignore all of these new spurious websocket errors. We needed to tell it to ignore the "INFO" lines which were bycatch of the websocket errors. The Websocket errors were actually already being ignored. I think. Anyway, third try is the charm, right?