Repository navigation
AbstractClientTransport.checkState builds a broken error message #1083
Description
AbstractClientTransport.checkState calls check(actualState == expected) { lazyMessage }. That returns the lambda itself instead of lazyMessage(actualState), so the exception text is a function's toString(). Nothing in the SDK calls the method, but it is protected API in the ABI dump, so subclasses can.
Expected: fix the call, or remove the method while the public API is being reviewed (#1038).
Activity
mvanhorn commentedon Oct 20, 2026
AbstractClientTransport.checkState returns lazyMessage itself from the check failure block instead of invoking it with actualState.
Invoke lazyMessage(actualState) when the state check fails. Add regression tests for the default message, custom message evaluation exactly once with the observed state, skipped evaluation when the state matches, and formatting after a forced state change.
#1132