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
When setting up and using multiple direct-tcpip channels concurrently there seem to be some kind of bug where the the different channels end up being confused and the wrong one used.
Reproduction steps
Server
On the server:
$ mkdir a b
$ echo -n a >a/index.html
$ echo -n b >b/index.html
$ python3 -m http.server 8001 --directory a &
$ python3 -m http.server 8002 --directory b &
Now when we issue requests at http://localhost:8001 we should expect a single a in response and b for :8002.
Client
On the client side set up a project with the following dependencies and code:
async-ssh2-lite = { version = "0.4.7", features = ["tokio"] }
bytes = "1.6.1"http-body-util = "0.1.2"hyper = { version = "1.4.1", features = ["client", "http1"] }
hyper-util = { version = "0.1.6", features = ["tokio"] }
tokio = { version = "1.38.1", features = ["macros", "rt", "rt-multi-thread"] }
When setting up and using multiple
direct-tcpip
channels concurrently there seem to be some kind of bug where the the different channels end up being confused and the wrong one used.Reproduction steps
Server
On the server:
Now when we issue requests at
http://localhost:8001
we should expect a singlea
in response andb
for:8002
.Client
On the client side set up a project with the following dependencies and code:
Client code
Expected
You get a stream of output where each
A
line has a response ofa
and eachB
line has a response ofb
.Actual
The text was updated successfully, but these errors were encountered: