You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
GraphBatch: #9242 is fixed in the engine; the tripwires flip and a refused close() must leave the wrapper open #191
ArcadeDB ArcadeData#9270 (26.10.1) makes GraphBatch.createVertices, flush, close, and a newEdge that fills the buffer refuse to run inside a transaction the caller opened (IllegalStateException) and leave it untouched. The CI snapshot image now carries it, so the seven strict xfail tests for ArcadeData#9242 in tests/test_graph_batch.py XPASS and fail the suite on every PR.
Measured through the bindings on the CI jar of upstream 5a90b0f, the refusal also exposes a bindings bug: GraphBatch.close() sets _closed in a finally block, so a close() the engine refused inside the caller's transaction marks the wrapper closed while the Java batch stays open. A second close() after the caller commits is then a no-op: the buffered edges are never written (2 edges where 3 are expected), and db.graph_batch() on that database fails with 'A GraphBatch is already in progress'.
Fix: keep the wrapper open when the engine refused because of the caller's transaction, turn the seven tripwires into plain tests that also assert the refusal, add a test for close() retried after the refusal, and rewrite the docs for the engine that has the fix while keeping the workaround for 26.9.1.
Activity
bindings: GraphBatch refuses a caller's transaction (PR ArcadeData#9270…