From 9ec2366870e7f4b49319dcab754f2cef2af8629c Mon Sep 17 00:00:00 2001 From: owenpearson Date: Wed, 28 Oct 2026 13:20:32 +0000 Subject: [PATCH 1/5] pubsub: take the millisecond timing options in seconds, as *_seconds TO3l1, TO3l2, TO3l7, TO3l10 and TO3l11 count disconnectedRetryTimeout, suspendedRetryTimeout, channelRetryTimeout, fallbackRetryTimeout and realtimeRequestTimeout in milliseconds, and ably-python took realtime_request_timeout, disconnected_retry_timeout, suspended_retry_timeout, channel_retry_timeout and fallback_retry_timeout in milliseconds too. Its three HTTP timing options took seconds, so a client's options came in two units with nothing in their names to say which. The five options now take seconds, as an int or a float, and are renamed realtime_request_timeout_seconds, disconnected_retry_timeout_seconds, suspended_retry_timeout_seconds, channel_retry_timeout_seconds and fallback_retry_timeout_seconds, defaulting to 10, 15, 30, 15 and 600. They read back from Options under the new names. The clock still counts milliseconds, so Options converts each one in a single place, seconds_to_ms, behind a private _