Errors
Fixes
On an incident, the « Corriger » (Fix) button starts writing the fix. You review the diff in Oxvel, then you open the PR and merge it.
From the button to the PR
- 1You click « Corriger » on the incident page.
- 2Oxvel writes the fix, and proves it when possible.
- 3The diff appears on the incident page. Nothing is written to GitHub yet.
- 4You review it and click « Ouvrir la PR » (Open the PR). It opens as a draft, on its own branch.
- 5You merge it yourself.
- 6Oxvel checks that the error doesn't come back.
The proven fix
In an isolated machine, Oxvel clones your repository read-only, writes a test that reproduces the error, applies the fix and runs the test again. The proof appears with the diff, then it is attached to the PR. It usually takes between 3 and 8 minutes.
Autopilot
When turned on in « Paramètres > Modèle » (Settings > Model), it starts the proven fix on its own as soon as the automatic analysis has explained a new error, even at night. When the fix is ready, the on-call person gets a message in the PagerDuty or Opsgenie alert, on Slack, on Discord and by email. It gives the cause, the proof and a link to the incident page. There, they review the diff and choose whether to open the PR or roll back to the previous deployment. Nothing is written to GitHub without them. 3 runs per day at most, up to €1.30 each from your monthly AI credit.
If CI fails
If the PR's tests fail on GitHub, Oxvel reads the logs and suggests a correction on the incident page. You review it, then click « Pousser sur la PR » (Push to the PR). It suggests 3 times at most.
Check that it worked
After the merge, Oxvel watches the error. If it doesn't come back for 2 hours, the fix is confirmed. The incident is closed in Sentry or in Oxvel and an incident report is written. The 20 minutes after the merge don't count, to give the deployment time to go out.