Skip to content

feat: report structured compiler error types - #41

Merged
banteg merged 1 commit into
vyperlang:masterfrom
charles-cooper:issue-40-structured-compiler-errors
Jul 27, 2026
Merged

feat: report structured compiler error types#41
banteg merged 1 commit into
vyperlang:masterfrom
charles-cooper:issue-40-structured-compiler-errors

Conversation

@charles-cooper

Copy link
Copy Markdown
Member

co-authored by gpt 5.6 sol

Summary

  • add source_error_type and target_error_type to JSON report schema v6
  • capture the concrete Vyper exception class at the managed compiler boundary, leaving the fields null when no typed exception is available
  • preserve the existing verbatim error text and existing compiler return codes under each attestation's exit_status.code

Fixes #40

@charles-cooper
charles-cooper requested a review from banteg July 27, 2026 05:06
@banteg
banteg marked this pull request as ready for review July 27, 2026 11:16

@banteg banteg left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the schema v6 propagation and managed-compiler error classification. Full local suite (887 tests), focused integration coverage, real Vyper 0.3.10/0.4.3 failure probes, and wheel smoke all pass.

@banteg
banteg merged commit 8fe7446 into vyperlang:master Jul 27, 2026
3 checks passed
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.

JSON report: include structured error kind and compiler return code for failed compiles

2 participants