New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
websocket client error about tokio #213
Comments
git pull the latest code and rerun the case, got the same error. stack backtrace: |
I have encounter the same 'no current timer' error, and have found a workaround if not fix. The updated PR #166 contains my workaround and plus a simplification for websocket-client. You can have a look at my workaround before this PR merged. |
@guoli-lyu |
But my question would be why is this error popping up ? |
This fails with a "no current timer" panic Referenced: actix/examples#213 Potentially fixed with: actix/examples#166
After a successful building...
$ target/debug/websocket-server
2019-12-20T07:23:21Z INFO actix_server::builder] Starting 4 workers
[2019-12-20T07:23:21Z INFO actix_server::builder] Starting server on 127.0.0.1:8080
HttpRequest HTTP/1.1 GET:/ws/
headers:
"sec-websocket-version": "13"
"upgrade": "websocket"
"host": "127.0.0.1"
"date": "Fri, 20 Dec 2019 07:23:42 GMT"
"sec-websocket-key": "WooAi1Tj/UX/JUbar8hI4w=="
"connection": "upgrade"
Ok(
Response HTTP/1.1 101 Switching Protocols
headers:
"upgrade": "websocket"
"sec-websocket-accept": "xrTk+NMx5mtLFlHB0En2jEduwMU="
"transfer-encoding": "chunked"
body: Stream
)
[2019-12-20T07:23:42Z INFO actix_web::middleware::logger] 127.0.0.1:56956 "GET /ws/ HTTP/1.1" 101 0 "-" "-" 0.036748
$ target/debug/websocket-client
ClientResponse HTTP/1.1 101 Switching Protocols
headers:
"date": "Fri, 20 Dec 2019 07:23:42 GMT"
"upgrade": "websocket"
"connection": "upgrade"
"sec-websocket-accept": "xrTk+NMx5mtLFlHB0En2jEduwMU="
"transfer-encoding": "chunked"
thread 'main' panicked at 'no current timer', /Users/wenjunwang/.cargo/registry/src/code.aliyun.com-738b7dba08a2a41e/tokio-0.2.4/src/time/driver/handle.rs:67:21
note: run with
RUST_BACKTRACE=1
environment variable to display a backtrace.The text was updated successfully, but these errors were encountered: