Ravi Teja

Results 28 issues of Ravi Teja

Is there a way to poll progress of a long running query? This is the equivalent c API I found http://duckdb.org/docs/api/c/api#duckdb_query_progress

https://github.com/inre/rust-mq/blob/master/mqtt3/src/write.rs#L74 Maybe all the writes should be replaced with `write_all` since `write` doesn't guarantee complete writes? This would be problem while doing synchronous request/response since you can't do a `read_incoming_mqtt`...

https://github.com/inre/rust-mq/blob/master/mqtt3/src/read.rs#L155 Hi @inre. Is that correct? Maybe you forgot to do `take(len)`?

Is it possible to use same client to subscribe (and read incoming messages) and publish at the same time? ``` loop { match client.await().unwrap() { Some(message) => println!("{:?}", message), None...

Reconnect is working but not as specified by `ReconnnectAfter` duration ``` opts.set_keep_alive(15); opts.set_reconnect(ReconnectMethod::ReconnectAfter(Duration::new(5,0))); let mut client = opts.connect(address.as_str(), netopt).unwrap(); client.subscribe(topic.as_str()).unwrap(); client.await().unwrap(); loop { match client.await() { Ok(result) => match result...

Size of hello world is about 650kb. Flash size of my router is about 8MB. Static linking might not be the right option if I want to flash multiple binaries....

We need a centralized control center to - Get an internal view of the broker. I.e broker metrics - Integration testing of broker. This will be like paho mqtt test...

https://docs.rs/opendal/latest/opendal/struct.BlockingOperator.html#method.write Write method seems to be taking owned buffer making it hard to re-use the buffer to prevent allocations. Is there a way around this: