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
Pin is_disconnect leader-code matrix and do_ping error propagation
Two regression fences on the sync dialect:
1. is_disconnect: existing coverage tested only NOT_LEADER (10250);
LEADERSHIP_LOST (10506) was in the LEADER_ERROR_CODES tuple but
untested. Iterate the full tuple and assert each member is
classified as a disconnect. Add a negative parametrised test
across common non-leader SQLite codes (1 / 5 / 14 / 19) to guard
against a broadened check misclassifying them.
2. do_ping: the narrow except tuple was tested for RuntimeError only;
programming-error categories (AttributeError, TypeError,
AssertionError) that signal real refactor bugs should propagate
too, not silently return False. Parametrised test fences each.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments