Skip to content
Sign up

flagon-io/g1t

public
00

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

gitagentscloudflarerustforgemcp
syntaqxA push to the default branch starts its runs about 8 seconds sooner, repos and work log every request while the ~60 s stalls are traced, and repos logs its slow answers with the time the caller waited. Measured on flagon-io/g1t over its last 35 pushes (the timeline's git.push times against each run's created_at and started_at): a push's first run is made 12 to 46 s after its event (usually 16 to 20), each further workflow 4 to 6 s after the one before, and a run's first job starts 1 to 3 s after it is made whenever the workspace has room. For 6e24edf2 the event was at 20:37:25.7, the actions consumer started at about 20:37:32.5 (two queue hops), Caches was made at 20:37:43.7, CI at 20:37:47.4 and Deploy at 20:37:52.8, each starting 1.4 to 2 s later. Of the 11 s inside the consumer before the first run, most was reading the twelve workflow files from repos one after another (blob at 300 to 400 ms each), twice: once to sync the workflows table for the default branch and once more, at the same commit, to start the runs. Now the sync hands back what it read, and on_event starts a default-branch push's runs from it while the branch is still at the pushed commit (read.head equals the push's after; otherwise it reads as before), and read_folders reads the files six at a time, in the tree's order. The waits of minutes some runs show (29aba25d: 7 to 8.5 min, 58def404: 5 min, Deploy runs: up to 28 min) are RUNNING_PER_WORKSPACE (four of a workspace's jobs at once) and Deploy's concurrency group, by design, not dispatch; nothing here changes them. Repos and work keep every invocation's logs (head_sampling_rate 1), with a comment to put them back to 0.1 once the stalls are found, and the deploy guide says so. Repos' p99 wall time in Workers Logs counts ctx.wait_until, which waits up to meters::FLUSH_EVERY_MS to write the meters; an RPC answer that takes a second or more now logs {"rpc", "answered_ms"} as JSON, which Workers Logs keeps as fields, so slow answers can be told from slow flushes; the svc entry of every answer's server-timing already gave callers the same time. Metering is unchanged. Checked: cargo test for g1t-actions-service (113), g1t-repos (341) and g1t-work (189), clippy for wasm32 on both services with no new warnings, node scripts/deploy.mjs manifest --check, and npm run test:deploy (92).