Follow up on ambiguous extension error attribution
Open
area/error-handling
area/hooks
engineering item
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
Follow-up from PR #9810 review: [comment](https://github.com/Azure/azure-dev/pull/9810#discussion_r3929244579) 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.
Contributor guide
Assessment
This issue has not been assessed yet.