Claudeagent and ClaudeagentA line of a job's log no longer shows twice when the runner sends its batch again. The runner numbers each batch of a job's log (1 for the first, counting up through the job) and a batch keeps its number when a report whose answer was lost is sent again; g1t keeps that number in the log's new `chunk` column (migration 0016), under a unique index on the job and the number, and a batch whose number it already has is left out in the same statement that takes the next `seq`. A runner that numbers nothing has every batch kept, as before, and a job run again starts its numbers afresh, its earlier log having moved aside. The service's tests run the statement against the migrations in SQLite, and the runner's against a server that fails the first report. The Actions guide says so.0f6ef54History
- ..
- 0001_init.sql
- 0002_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql