You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feed confirmed code diagnostics into Low without retrying environment failures #2
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.
Activity