Custom TCP connect timeout ? about tokio-modbus

[MightyPork]

any progress / plans for this?

it made me ditch the sync client and write this async abomination instead (my first time using futures, too)

let mut rt = tokio::runtime::Runtime::new().unwrap();
rt.block_on(async {
        let mut ctx = tokio::time::timeout(Duration::from_secs(3),
                                           tokio_modbus::client::tcp::connect_slave(socket_addr, Slave(12)))
            .await.unwrap().unwrap();

        // more stuff
    });

[flosse]

@jvelo Sorry for the late reply.
The TCP connection currently is managed by the deprecated tokio-proto crate that no longer is maintained. Unfortunately there is no drop-in replacement for that.
I already ask for a possible replacement more than a year ago (tokio-rs/tokio-proto#202 (comment)) but there is not really a progress on that :(
This is why we're going to remove the dependency entirely. The corresponding issue is discussed in #18
Probably we first will release a v0.3.x (#10 ) and will work on a tokio-proto replacement in a v0.4.x release.
Until then you might use a custom wrapper with a timeout feature.

[glennpierce]

any progress / plans for this?

it made me ditch the sync client and write this async abomination instead (my first time using futures, too)

let mut rt = tokio::runtime::Runtime::new().unwrap();
rt.block_on(async {
        let mut ctx = tokio::time::timeout(Duration::from_secs(3),
                                           tokio_modbus::client::tcp::connect_slave(socket_addr, Slave(12)))
            .await.unwrap().unwrap();

        // more stuff
    });

This saved me. Ugly but works