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
- ..
- advisories.rs
- code_scanning.rs
- config.rs
- deps.rs
- fixes.rs
- history.rs
- lib.rs
- manifests.rs
- overview.rs
- patterns.rs
- planning.rs
- pull_text.rs
- ranges.rs
- registries.rs
- resolved.rs
- schedule.rs
- secret_alerts.rs
- security_updates.rs
- store.rs
- suite.rs
- suite_store.rs
- summaries.rs
- supply_chain.rs
- timezones.rs
- update_store.rs
- updates.rs
- version_updates.rs
- yaml.rs