In terms of Telegram bot API the maximum polling time of getUpdatesis referred to as timeout. That is if there are pending updates, Telegram will return them immediately. In the other case, it will wait for timeout seconds and then answer with an empty list.
The telegram-bot Rust library has its own notion of timeouts. getUpdates' timeout [i
It should be quite similar to the other tests which are currently in place.
It should isolate a follower node, write a data to the cluster which will cause that node to fall behind into lagging state, but not into snapshotting state.
It should then spawn a task which will continue to write data to the cluster.
It looks like Nitox doesn't support client verification as of now. I made some quick changes to pass TLS config to the native-tls connector. When I tested this, I'm getting:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: TlsError(Ssl(Error { code: ErrorCode(1), cause: Some(Ssl(Erro
In terms of Telegram bot API the maximum polling time of
getUpdatesis referred to astimeout. That is if there are pending updates, Telegram will return them immediately. In the other case, it will wait for timeout seconds and then answer with an empty list.The telegram-bot Rust library has its own notion of timeouts. getUpdates' timeout [i