Skip to content

Feed confirmed code diagnostics into Low without retrying environment failures #2

Open

Description

@onoderakosen89

Problem

The bundled Node.js checker and pytest runner conservatively classify non-assertion errors as unknown. The repair loop stops on an unknown result. That is appropriate when the check cannot run, but also means a diagnosable source syntax error can stop the loop before Low receives any repair turn.

Acceptance criteria

  • Start with one existing checker that can reliably identify a code diagnostic, such as a Node syntax check. Include the file and location when available.
  • A confirmed code diagnostic reaches the Low repair callback and the same check is rerun afterward. Keep the check result and the reason it is or is not actionable distinct.
  • An unavailable runner, timeout, or ambiguous setup failure stays inconclusive and does not trigger a repair or effort increase.
  • Test a known-good case, an actionable failure and successful recheck, and a non-actionable failure. Do not classify all nonzero exits as actionable.

Related positioning: #1.

Activity

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