fix(hermes): repair ariadne/415 #5
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "hermes-repair/415"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hermes repair proposal for incident ariadne/415
Incident: ariadne/415
File:
ariadne/utils/errors.pyAnalysis: Build 415 failed only because test_safe_error_detail_http_status_json expected the HTTP 400 JSON errorMessage value, but safe_error_detail returned only "http 400". The immediately preceding refactor omitted the errorMessage key while preserving error and message handling. Coverage and the quality contract passed; this is a localized application regression.
Rationale: Restore support for the existing errorMessage response payload with a one-line fallback addition, satisfying the failing test without changing behavior for error or message payloads.
Proposed by Hermes; validated and pushed by Ariadne; requires human review — no automatic merge.
Closing — deliberately seeded defect, reverted directly.
This run existed to verify that structured test evidence reaches triage now that the
junitplugin is installed. It did: the bundle carriedfailed_testswith the failing test name, class and assertion, plusfirst_failed_stage: Enforce quality gate. Both were empty for every previous incident.The effect on file selection is visible. Before junit, candidate selection offered
ariadne/app.pyfirst — the wrong file. With junit it offeredtests/test_utils.pyfirst and droppedapp.pyentirely, and Hermes choseariadne/utils/errors.pycorrectly.Closed rather than merged for the same reason as #3: the patch is correct for the failing test but reorders key precedence relative to the original (
error or message or errorMessageversuserrorMessage or error or message), so it is not a faithful restoration. Ariadne's duplicate guard also refuses new proposals while ahermes-repair/*pull request is open.Pull request closed