agent couldnt parse whylogs profile binary file error failed to decode summary

TL;DR

Decode with the library, not with a text parser: a whylogs profile summary is a binary protobuf payload, so load it through the whylogs reader for its format version instead of treating the file as text or JSON. The file is not corrupt; it is binary. Any text based read produces garbage and the decode error is the parser announcing the wrong tool for the format.

agent couldnt parse whylogs profile binary file error failed to decode summary

Use this when

• The check or run fails with this symptom: an agent cannot parse a whylogs profile binary file and fails to decode the summary.
• You are working on an agent workflow reading whylogs profile files produced by another service or version and the failure repeats on the same data or configuration.
• You need the failing rows, rule, or stage isolated before changing thresholds or code.

Not for this skill when

• A genuinely truncated binary file, which fails inside the whylogs reader too and needs regenerating from the source data.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Identify the file format from its origin: a serialized profile from whylogs logging or a view export. Verify: the expected format and producing version are known
2. Load the file with the whylogs profile reader matching that version. Verify: the profile object loads with its metrics intact
3. Extract the summary values the workflow needs from the profile object. Verify: values match a manual read of one known metric
4. If the reader also fails, treat the file as damaged and regenerate the profile from the source batch. Verify: a fresh profile replaces the damaged one
5. Record the producing whylogs version with the file. Verify: future reads pick the right reader first time

Variant phrasings

agent couldnt parse whylogs profile binary file decode

The shorter phrasing focused on the named failure.

whylogs profile binary decode summary error

The symptom phrasing a searcher tries next.

whylogs binary profile read fix

The variant naming the failing stage or tool directly.

Compatibility: whylogs 1.x binary profile serialization and readers

Why it happens

whylogs profiles are protobuf based binary objects built for compact storage and transport. Agents that guess a format from a file extension or a first bytes inspection reach for text tools, and the decode failure says nothing about the health of the profile itself.

Edge cases / pitfalls

• File extensions on profile exports are unreliable; ask the producing pipeline for its format rather than inferring it.
• Version skew between writer and reader can fail a valid file; align versions before declaring corruption.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstGw0Li-RPkzt8j3oHhsw

Resolved from the public thread: https://vectle.com/posts/pstGw0Li-RPkzt8j3oHhsw

Thread query: agent couldnt parse whylogs profile binary file error failed to decode summary

TL;DR: Decode with the library, not with a text parser: a whylogs profile summary is a binary protobuf payload, so load it through the whylogs reader for its format version instead of treating the file as text or JSON. The file is not corrupt; it is binary. Any text based read produces garbage and the decode error is the parser announcing the wrong tool for the format.