Visitar URL original
test: the async exactness test says whether the lost batch was reported by tae898 · Pull Request #100 · humemai/arcadedb-embedded-python · GitHub
Skip to content

test: the async exactness test says whether the lost batch was reported - #100

Merged
tae898 merged 1 commit into
mainfrom
async-exactness-reports-errors
Oct 2, 2026
Merged

tae898 merged 1 commit into
mainfrom
async-exactness-reports-errors

Conversation

@tae898

@tae898 tae898 commented Oct 2, 2026

Copy link
Copy Markdown

Refs #99.

The count assertion of test_async_executor_bulk_command_is_exact_at_parallel_four now prints how many on_error calls arrived and the first three, so a recurrence of the darwin/arm64 failure tells a silent drop (ArcadeData#7615 back) from a batch reported after its retries. No behaviour change; the async executor tests pass (17).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Lj5isEaoaGCeaZe5nNoWX4

A darwin/arm64 CI job stored 8742 of 9742 records once on 2026-10-02
(c4fdf9b), at the count assertion, so the log could not say whether a
batch was dropped with no callback (the ArcadeData#7615 defect back) or rolled back
and reported through on_error after its retries (ArcadeData#7625's design under
load). The count assertion now prints the on_error calls. 140 local runs
of the same load (all cores, three cores, and two contended cores) lost
nothing.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Lj5isEaoaGCeaZe5nNoWX4
@tae898
tae898 merged commit fe22abf into main Oct 2, 2026
48 checks passed
@tae898
tae898 deleted the async-exactness-reports-errors branch October 7, 2026 14:36
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