Khaled Karam

@kamyuentse nope, I didn't get anything new output using `trace` level log.

@kamyuentse this is my snippet main.rs ```rust extern crate bytes; extern crate futures; extern crate tokio_io; extern crate tokio_proto; extern crate tokio_service; use tokio_proto::TcpServer; use std::io; use std::str; use bytes::BytesMut;...

This is the logs result when I made the request that returned the error ``` DEBUG:tokio_core::reactor : loop poll - Duration { secs: 6, nanos: 939381975 } DEBUG:tokio_core::reactor : loop...

yup, I reached the same point debugging. And it didn't reach the second trace `frame decoded from buffer` meaning there was an error alright. Actually, I'm suspecting ```rust fn bind_transport(&self,...

the silently part, shouldn't it log the error message or return it. Or should I change something to allow that to happen?

no no, I agree with you. it should close the connection alright (which I want). but in the example, the `decode` method returns an error with message `Err(io::Error::new(io::ErrorKind::Other, "invalid UTF-8"))`,...

That would be a great idea if you want to keep 0.8 tied with rustc 1.15

yup, that'd be enough until Rust 2018 is fully complete I think. I was planning to contribute but I wanted first to clear the deprecated stuff and fix the `clippy`...

I too have the same problem in Fedora **node:** `v8.9.1` **npm:** `v5.5.1` **Distro Details:** ``` LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: Fedora Description: Fedora release 27 (Twenty Seven) Release: 27 Codename:...

@zoumi have you found a way to do it?