-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
Labels
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingwasiIssues pertaining to WASIIssues pertaining to WASI
Description
In the following snippet:
let mut accept = sock.listen().unwrap();
futures::join!(
async {
let next = accept.next().await.unwrap();
assert_eq!(next.get_address_family(), sock.get_address_family());
assert_eq!(next.get_keep_alive_enabled(), sock.get_keep_alive_enabled());
assert_eq!(
next.get_keep_alive_idle_time(),
sock.get_keep_alive_idle_time()
);
assert_eq!(
next.get_keep_alive_interval(),
sock.get_keep_alive_interval()
);
assert_eq!(next.get_keep_alive_count(), sock.get_keep_alive_count());
assert_eq!(next.get_hop_limit(), sock.get_hop_limit());
// The following asserts fail.
assert_eq!(
next.get_receive_buffer_size(),
sock.get_receive_buffer_size()
);
assert_eq!(next.get_send_buffer_size(), sock.get_send_buffer_size());
},
async {
client.connect(local_addr).await.unwrap();
}
);The values for get_receive_buffer_size() and get_send_buffer_size() are different between the listener and the handler socket.
According to the spec:
The following properties are inherited from the listener socket:
address-familykeep-alive-enabledkeep-alive-idle-timekeep-alive-intervalkeep-alive-counthop-limitreceive-buffer-sizesend-buffer-size
Platform specific information:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingwasiIssues pertaining to WASIIssues pertaining to WASI
Type
Projects
Status
Backlog