Python repair

Failed commit and CI evidence

• Placebo case python-repair-missing-await: A missing await returns a coroutine instead of a value. The repair must add the await and keep the unittest.
• Failing command: python3 -B -m unittest discover -s tests -p 'test_*.py'
• Error excerpt: AssertionError: <coroutine object fetch_name at 0x7ffff6f950> != 'Ada'\n\n----------------------------------------------------------------------\nFAIL: test_fetches_name (test_app.AppTest.test_fetches_name)\n----------------------------------------------------------------------\nTraceback (most recent call last):\n File \"/usr/local/lib/python3.13/asyncio/runners.py\", line 118, in run\n return self._loop.run_until_complete(task)\n ~~~~~~~~~~~~~^^^^^^^^^^^\n File \"/usr/local/lib/python3.13/asyncio/base_events.py\", line 725, in run_until_complete\n return future.result()\n ~~~~~~~~~~~~~^^^\n File \"/workspace/tests/test_app.py\", line 8, in test_fetches_name\n self.assertEqual(fetch_name(), \"Ada\")\n ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^\nAssertionError: <coroutine object fetch_name at 0x7ffff6f950> != 'Ada'
• Repository local/fixture · run local-fixture · runtime python
• Recorded workflow run

Nano diagnosis and confidence

Failure class

test-assertion

Confidence

96%

Signals

• AssertionError: <coroutine object fetch_name at 0x7ffff6f950> != 'Ada'
• mechanical:test-assertion
• signature:\bAssertionError\b

Diagnosis recovery

• Initial diagnosis retained: test-assertion. Recovery: insufficient — invalid-hypotheses.
• Observed command: python3 -B -m unittest discover -s tests -p 'test_*.py'
• Executed command: uv run --offline --no-sync python3 -B -m unittest discover -s tests -p 'test_*.py'
• These bounded observations do not measure live repair quality.

Clean audit branch and Ultra verdict

Not run. No candidate survived for adversarial audit.

Final outcome

Gave up Recorded live result

Sutura never merges a generated repair. A gave up result still needs human review.

Check a patch this page did not produce

This run did not record an exact failing commit and policy commit, so both are shown as placeholders. Verification is always tied to exact commits. A patch cannot ask for a more permissive policy by carrying one, and no green log is accepted in place of execution.

sutura verify \
  --case-dir <checkout> \
  --source-sha <failing commit> \
  --policy-base-sha <trusted policy commit> \
  --candidate-diff <patch file> \
  --failing-command diagnosed \
  --format json

The same route runs as a GitHub Action and needs no repository write access. Uploading a patch stays a command-line and Action route; this page never runs one.