Skip to content

refresh: batch every 5 edits, not 3, where a rebuild is slow - #1879

Merged
swapnilpaliwal-sd merged 1 commit into
apps/integration-0.1.9from
refresh/batch-5
Oct 9, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
apps/integration-0.1.9from
refresh/batch-5

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

Where the last rebuild took 20 s or more, edits now count toward a rebuild until the fifth instead of the third (AXIOMCODE_REFRESH_BATCH default 3 → 5; 1 still turns batching off).

Unchanged:

  • A query never blocks: it answers from the last good graph and marks rows from edited files (may be out of date).
  • The end of a turn, a prompt, session start, the MCP timer and every query still refresh at once.
  • Repositories whose rebuild takes under 20 s still rebuild after every edit.

Test

tests/refresh.py --lang python: the slow-repo batch check now makes four edits and a shell command (no rebuild), then the fifth (rebuild). All four batching checks pass.

Eight other checks in that file fail on apps/integration-0.1.9 without this change too (changed / test-impact before vs after refresh, commit and pull baselines, a new untracked file). The failing set is identical with and without this change.

On a repository whose last rebuild took 20 s or more, edits now count toward
a rebuild until the fifth (AXIOMCODE_REFRESH_BATCH default 3 -> 5). Queries
still answer from the last good graph meanwhile, marking rows from edited
files, and the end of a turn, a prompt, session start, the timer and every
query still refresh at once.

tests/refresh.py: the slow-repo batch check now makes four edits and a shell
command (no rebuild), then the fifth (rebuild).

Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit 299b63b into apps/integration-0.1.9 Oct 9, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the refresh/batch-5 branch October 9, 2026 21:40
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