Skip to content

Follow up on ambiguous extension error attribution #9876

Description

@huimiu

Follow-up from PR #9810 review: comment notes that multiple lifecycle-handler failures can mix classification with invocation metadata or cause types from different error branches.

Later, collect metadata across joined errors and emit extension attribution only when it is unambiguous, with regression coverage for multiple failing handlers.

Activity

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

Metadata

Metadata

Labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions