[google/syzkaller] 8e1c15: dashboard/app: journal failed commands

[Aleksandr Nogikh]

Branch: refs/heads/gh-readonly-queue/master/pr-7316-1d9407ad5a662c921fc0d659cf022b438c0bde91
Home: https://github.com/google/syzkaller
Commit: 8e1c15172f6ef17377fb7620dd985ae25d6faba8
https://github.com/google/syzkaller/commit/8e1c15172f6ef17377fb7620dd985ae25d6faba8
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2026-05-19 (Tue, 19 May 2026)

Changed paths:
M dashboard/app/ai.go
M dashboard/app/ai_report.go
M dashboard/app/ai_report_lore_test.go
M dashboard/app/aidb/crud.go
M dashboard/app/aidb/entities.go
A dashboard/app/aidb/migrations/18_journal_error.down.sql
A dashboard/app/aidb/migrations/18_journal_error.up.sql
M dashboard/app/templates/ai_job.html

Log Message:
-----------
dashboard/app: journal failed commands

When lore-relay encounters a logical command failure (e.g. attempting to
upstream an iteration without a patch), it replies to the user. Because
these failures were never recorded in the dashboard's Journal, lore-relay
would re-process them upon restart, resulting in an endless loop of
duplicate error emails.

Fix this by recording logical command rejections in the Journal. Add a new
Error column to the Journal table and UI to surface the failure reasons.
This ensures `aidb.IsCommandProcessed` correctly identifies failed commands
as processed, breaking the retry loop.



To unsubscribe from these emails, change your notification settings at https://github.com/google/syzkaller/settings/notifications

[Aleksandr Nogikh]

Branch: refs/heads/master