Phase 6.1 observation. Every plumb lint <real-url> run dumps dozens of WARN chromiumoxide::handler: WS Invalid message: data did not match any variant of untagged enum Message lines to stderr. These are upstream chromiumoxide protocol parsing warnings (see also #233 for the Linux Next.js timeout symptom of the same upstream bug). Either filter the warning at our log level (suppress chromiumoxide::handler WARN by default) or wait for an upstream fix. Filtering would clean up CI logs and make our own diagnostics easier to spot.
Phase 6.1 observation. Every
plumb lint <real-url>run dumps dozens ofWARN chromiumoxide::handler: WS Invalid message: data did not match any variant of untagged enum Messagelines to stderr. These are upstream chromiumoxide protocol parsing warnings (see also #233 for the Linux Next.js timeout symptom of the same upstream bug). Either filter the warning at our log level (suppresschromiumoxide::handlerWARN by default) or wait for an upstream fix. Filtering would clean up CI logs and make our own diagnostics easier to spot.