Skip to content

Preserve diagnostic evidence when a repair-loop callback throws #3

Closed

Description

@onoderakosen89

Problem

The repair loop catches a failed repair call but does not catch exceptions from the initial check, a recheck, or the diff reader. A diff read in the repair catch can also throw. These failures can reject the whole call rather than return the consultation, including after a repair may already have modified the project.

Acceptance criteria

  • Operational exceptions identify the failing stage (initial check, repair, recheck, or diff read) and do not present the work as verified.
  • Return a structured consultation with the latest available observation, completed attempts, and last known diff, or an explicit indication that the diff is unavailable.
  • Keep useful sanitized error information without dumping secrets or raw environment output.
  • Cover failures before and after a repair and a diff-read failure while handling an earlier repair error. Keep invalid caller configuration separate from operational failures.

Related positioning: #1.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions