Skip to content

Add sanitized parse-error report mode#19

Open
qingfeng312 wants to merge 1 commit into
9904099:mainfrom
qingfeng312:qingfeng/parse-error-report-1
Open

Add sanitized parse-error report mode#19
qingfeng312 wants to merge 1 commit into
9904099:mainfrom
qingfeng312:qingfeng/parse-error-report-1

Conversation

@qingfeng312

Copy link
Copy Markdown

Summary

  • Adds --parse-error-report to tools/log_aggregator.py for sanitized JSON parser failure reporting.
  • Captures parser type, file path, line number, and redacted error text without changing the normal parsed-log output.
  • Adds a focused smoke script covering malformed JSON, non-object JSON, valid JSON, and text fallback logs.
  • Includes the generated diagnostic JSON from python3 build.py; no encrypted .logd artifact was produced locally.

/claim #1
Closes #1

Testing

  • python3 -m py_compile tools/log_aggregator.py tools/log_aggregator_parse_error_smoke.py
  • python3 tools/log_aggregator_parse_error_smoke.py
  • git diff --check
  • python3 build.py generated diagnostic/build-2b54872c.json; frontend and v2-market-stream passed, while backend/market/engine/compliance/nfc/openapi modules failed locally because required toolchains or platform-specific build support were unavailable (cargo, go, cmake, Java runtime, luac, ghc, and macOS MAP_HUGETLB).

Checklist

  • I ran the focused validation commands above.
  • I included the generated diagnostic JSON.
  • I included an encrypted .logd artifact. It was not created by the local build run; the included diagnostic JSON records the failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[$40 BOUNTY] [Python] Add sanitized parse-error reports for log aggregation

1 participant