You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run the node with the following RUST_LOG="interledger=TRACE,warp" and connect to an account using BTP and then disconnect the client. The logging with spam indefinitely as far as I can tell.
2020-03-11T13:44:30.679783+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.679828+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.679873+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.679921+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.679965+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.680009+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.680054+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.680098+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
2020-03-11T13:44:30.680141+00:00 DEBUG warp::filters::ws: websocket poll error: Trying to work with closed connection
This probably has been fixed for some time now, as the current 629f8b5 lockfile has 0.2.5 and the linked issue was fixed in 0.2.2. Commit b1fcbeb updated from 0.2.1 to 0.2.2.
Just out of interest, what btp client/lib/code/tool did you use to connect and disconnect @matdehaast? Would be good to have repro instructions just to document.
If you run the node with the following
RUST_LOG="interledger=TRACE,warp"
and connect to an account using BTP and then disconnect the client. The logging with spam indefinitely as far as I can tell.Some preliminary investigation seems to point to this
seanmonstar/warp#446
seanmonstar/warp#257
The text was updated successfully, but these errors were encountered: