Algis DumbrisandClaude Opus 4.6 64c68c22be fix(014): prevent stuck runs by creating K8s Job before DB insert ...

The reactor was inserting the run record first, then creating the K8s
Job, then updating the record with the job name. If the update failed
(SQLITE_BUSY), the run would be stuck in 'running' with no job name,
making it invisible to the poller.

Now: create K8s Job first, then insert the run record with job name
already set in a single atomic write.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-26 06:09:16 +02:00

..

notifier.go

feat(014): implement reactive agent triggering engine

2026-03-25 17:42:48 +02:00

poller.go

feat(014): add Prometheus metrics, Grafana dashboard, volume mounts, resource tuning

2026-03-25 22:15:54 +02:00

reactor_test.go

feat(014): implement reactive agent triggering engine

2026-03-25 17:42:48 +02:00

reactor.go

fix(014): prevent stuck runs by creating K8s Job before DB insert

2026-03-26 06:09:16 +02:00

store.go

feat(014): implement reactive agent triggering engine

2026-03-25 17:42:48 +02:00