Full Error:

thread 'main' panicked at 'can call blocking only when running on the multi-threaded runtime', /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/macros.rs:13:23

Minimal app:

use actix_web::{App, HttpServer};
use sqlx::sqlite::SqlitePool;

#[actix_web::main]
async fn main() -> std::io::Result<()> {
    SqlitePool::connect("sqlite://foo").await.unwrap();

We have a fancy logo from the new tokio website, we should go through the code base and update it in every spot we use the old one.

https://github.com/tokio-rs/website/blob/master/public/img/icons/tonic.svg

Steps to reproduce

• futures-preview = { version = "0.3.0-alpha.19", features = [ "async-await" ] } in Cargo.toml as recommended in §3.1.
• Try to build the example in https://book.async.rs/tutorial/sending_messages.html

use futures::channel::mpsc; // 1
use futures::sink::SinkExt;
use std::sync::Arc;

type Sender<T> = mpsc::UnboundedSender<T>; // 2
type Receiver<T> = 

right now the popup uses a fixed width, it should use a dynamic one to show more information on wider terminal sizes:

$cargo run

Finished dev [unoptimized + debuginfo] target(s) in 0.13s
Running /home/folaht/testbot/devlohpmaq/target/debug/testbot
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })', src/main.rs:10:15
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

`$strace

Here is a rough idea of what this test should do:

• 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.
• Just after it is spawne

While investigating how to use rlua-async along with actix (see Ekleog/rlua-async#1 (comment)), I noticed that actix' block_on function requires a 'static bound.

I have searched the bug tracker, but can't see a reason why this would be required, and tokio's block_on [does not require it](https://docs.rs/tokio/0.2.22/tokio/runtime/struct.Runtime.html#method

Extend Session api to getting time until a key in the session will expire. Similar to Redis command ttl.

Extend Session api to reset ttl back to the initial time. For sessions with Redis, the expire command could be used.