You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 20ed0fa
Browse filesBrowse the repository at this point in the historyBrowse files
fix(analyzers): budget GIF walks and close image-cache gaps
- Bound GIF sub-block walks by count (2,000,000) instead of
absolute bytes so benign multi-megabyte frames stay COMPLETED;
flag every pre-trailer stop.
- Fill and publish image text caches for every input shape and
drop the runner's raw extraction fallback, so analyzers never
re-extract outside the shared deadline.
- Decode inline data: URIs per RFC 2397 and record
inline_image_decode_error for malformed payloads.
- Document the 512-character markdown destination bound; run the
compiled-graph image test from tests/nodes so CI executes it.
Signed-off-by: Yoseph Zuskin <[email protected]>
Co-Authored-By: OpenCode DeepSeek V4.1 Flash Free (1M context) <[email protected]>
`image_inventory` lists per-skill `local_images` (resolved markdown targets plus loose image files, no verdicts), `remote_images` (remote citations as scheme-plus-host only, never fetched), and `inline_images` (`data:` image URIs as MIME-plus-size summaries, never content). Exactly one inventory truncation shape exists: entry, line, deadline, or inline-size pressure appends a single `PARTIAL` row naming the output limit, and the public projection carries the same bound information.
138
138
139
-
Embedded text is extracted stdlib-only (PNG `tEXt`/`iTXt`/`zTXt`/`eXIf`, JPEG `COM` plus EXIF `UserComment`/`ImageDescription`/`XPComment`, GIF comments) once per image under the shared deadline and routed through the static patterns; findings carry an `image-text-layer` tag whose line numbers point into the extracted text, not file bytes. Text past a bound yields its bounded prefix and the image's static row reads `PARTIAL` with a size reason, never `COMPLETED`. Deliberate gaps: pixel decoding (no OCR), remote fetching, GIF plain-text extensions, WebP/BMP text layers, COM segments past JPEG scan data (progressive scans), JPEG XMP, and rendered/QR/steganographic content (needs the separate vision design).
139
+
Embedded text is extracted stdlib-only (PNG `tEXt`/`iTXt`/`zTXt`/`eXIf`, JPEG `COM` plus EXIF `UserComment`/`ImageDescription`/`XPComment`, GIF comments) once per image under the shared deadline and routed through the static patterns; findings carry an `image-text-layer` tag whose line numbers point into the extracted text, not file bytes. Text past a bound yields its bounded prefix and the image's static row reads `PARTIAL` with a size reason, never `COMPLETED`. Inline `data:` images are inventoried only from markdown destinations of at most 512 characters; the reference extractor drops longer destinations, so the 8-image and 1 MB inline caps rarely bind. GIF walks are bounded by sub-block count (not bytes), so a benign multi-megabyte frame stays `COMPLETED`. A PNG chunk length that overruns the file ends the chunk walk silently by design: the chunks already read were complete, and the remaining bytes are not a well-formed chunk stream (corrupt container, not a lost text layer). Deliberate gaps: pixel decoding (no OCR), remote fetching, GIF plain-text extensions, WebP/BMP text layers, COM segments past JPEG scan data (progressive scans), JPEG XMP, and rendered/QR/steganographic content (needs the separate vision design).
140
140
141
141
A subtlety is that component coverage can still read **100%** for AE6: analyzer work completed on each file, while a separate system event records unresolved interpretation. Consumers must use `is_complete` and the ledger, not the coverage percentage alone. No new telemetry platform is needed to explain these decisions; the existing public fields distinguish the causes.
0 commit comments