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
test(qwp): pin the sf_sync_interval_millis config rejection paths
Both new user-visible rejection branches for sf_sync_interval_millis
shipped untested: the out-of-range guard (<=0, or past the
Long.MAX_VALUE/1_000_000 nanosecond-overflow boundary) and the
non-WebSocket transport guard in the config-string parser.
Add three cases to SfFromConfigTest:
- testSfSyncIntervalRejectsZero: =0 is a realistic operator typo,
rejected with "sf_sync_interval_millis is out of range".
- testSfSyncIntervalOverflowBoundary: two-sided pin of the millis->nanos
overflow guard -- Long.MAX_VALUE/1_000_000 is honored with exact nanos,
one millisecond more is rejected -- so a later change to the operator
or the divisor cannot regress silently.
- testSfSyncIntervalRejectsOnNonWebSocketTransport: an http config is
rejected with "sf_sync_interval_millis is only supported for WebSocket
transport".
0 commit comments