Skip to content

plugin: a slow graph rebuilds after 7 edits instead of 5 - #1937

Merged
swapnilpaliwal-sd merged 1 commit into
apps/integration-0.1.10from
feat/refresh-batch-7
Oct 13, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
apps/integration-0.1.10from
feat/refresh-batch-7

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

Where the last build took 20 s or more (AXIOMCODE_REFRESH_BATCH_ABOVE), edits are batched and the Nth edit starts the background rebuild. This moves the default from 5 to 7.

Unchanged: a repository whose build is under 20 s still rebuilds after every edit; the end of a turn, a prompt, a session start, the timer and every query still refresh at once; AXIOMCODE_REFRESH_BATCH still overrides it (1 = off).

Checked: with a 60 s last build, edits 1-6 only count and the 7th starts the rebuild; a Stop flushes the batch; a 5 s build rebuilds on every edit. tests/freshness.py 118/118. tests/refresh.py fails the same 5 checks on the base branch in this environment (builds without a built parser), unchanged by this commit.

Where the last build took 20 s or more, edits are batched and the Nth one starts the rebuild. Seven lets a typical
multi-file change land before the graph rebuilds. The end of a turn, a prompt, a session start and every query still
refresh at once, so an answer never waits on the batch. AXIOMCODE_REFRESH_BATCH still overrides it (1 = off).

Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit 5f281c9 into apps/integration-0.1.10 Oct 13, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the feat/refresh-batch-7 branch October 13, 2026 01:37
This was referenced Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant