Add cancelation on tcpip.stack-socket#443
Conversation
|
I'm not sure I understand the patch. What is the goal in semantics that you try to achieve? Why are there some changes to Is it possible to formulate a test case with the desired semantics (to see what is failing at the moment, and what the intention is)? |
|
What is the advantage of using a |
12b667c to
f235dc2
Compare
Yes, I forget to apply such change on all stacks. Now it's fixed by a forced-push.
Currently, the master socket used to listen is not properly closed which leads an error when you want to launch multiple times sequentially a server on a specific port. Such situation mostly appears when we do some tests and I got several times the
This is where @talex5 should have a better explanation than me. |
|
I think we are ready for a release 👍 . |
CHANGES: * Add cancelation on `tcpip.stack-socket` (@dinosaure, @talex5, @hannesm, mirage/mirage-tcpip#443) * Ensure that listen really binds the given socket before creating a task on `tcpip.stack-socket` (@dinosaure, @hannesm, mirage/mirage-tcpip#439) * Add `ppx_cstruct` as a dependency (@hannesm, @dinosaure, mirage/mirage-tcpip#439) * Upgrade to ocamlformat.0.17.0 (@dinosaure, mirage/mirage-tcpip#442) * Drop the support of OCaml 4.08.0 (@dinosaure, mirage/mirage-tcpip#442) * Use the usual layout to compile freestanding C stubs and link them to a Solo5 unikernel (@dinosaure, @hannesm, mirage/mirage-tcpip#441) **breaking changes** C stubs are prepended by `mirage_`. Symbols such as checksum's symbols are `caml_mirage_tcpip_*` instead of `caml_tcpip_*` `tcpip.unix` is a fake sub-package and user does not it anymore, he can safely remove it from its project. * Conflict with `< ocaml-freestanding.0.4.1` (@hannesm, mirage/mirage-tcpip#441)
CHANGES: * checksum stubs: Drop `caml_` from their name (@hannesm, mirage/mirage-tcpip#445) * Add cancelation on `tcpip.stack-socket` (@dinosaure, @talex5, @hannesm, mirage/mirage-tcpip#443) * Ensure that listen really binds the given socket before creating a task on `tcpip.stack-socket` (@dinosaure, @hannesm, mirage/mirage-tcpip#439) * Add `ppx_cstruct` as a dependency (@hannesm, @dinosaure, mirage/mirage-tcpip#439) * Upgrade to ocamlformat.0.17.0 (@dinosaure, mirage/mirage-tcpip#442) * Drop the support of OCaml 4.08.0 (@dinosaure, mirage/mirage-tcpip#442) * Use the usual layout to compile freestanding C stubs and link them to a Solo5 unikernel (@dinosaure, @hannesm, mirage/mirage-tcpip#441) **breaking changes** C stubs are prepended by `mirage_`. Symbols such as checksum's symbols are `caml_mirage_tcpip_*` instead of `caml_tcpip_*` `tcpip.unix` is a fake sub-package and user does not it anymore, he can safely remove it from its project. * Conflict with `< ocaml-freestanding.0.4.1` (@hannesm, mirage/mirage-tcpip#441)
CHANGES: * checksum stubs: Drop `caml_` from their name (@hannesm, mirage/mirage-tcpip#445) * Add cancelation on `tcpip.stack-socket` (@dinosaure, @talex5, @hannesm, mirage/mirage-tcpip#443) * Ensure that listen really binds the given socket before creating a task on `tcpip.stack-socket` (@dinosaure, @hannesm, mirage/mirage-tcpip#439) * Add `ppx_cstruct` as a dependency (@hannesm, @dinosaure, mirage/mirage-tcpip#439) * Upgrade to ocamlformat.0.17.0 (@dinosaure, mirage/mirage-tcpip#442) * Drop the support of OCaml 4.08.0 (@dinosaure, mirage/mirage-tcpip#442) * Use the usual layout to compile freestanding C stubs and link them to a Solo5 unikernel (@dinosaure, @hannesm, mirage/mirage-tcpip#441) **breaking changes** C stubs are prepended by `mirage_`. Symbols such as checksum's symbols are `caml_mirage_tcpip_*` instead of `caml_tcpip_*` `tcpip.unix` is a fake sub-package and user does not it anymore, he can safely remove it from its project. * Conflict with `< ocaml-freestanding.0.4.1` (@hannesm, mirage/mirage-tcpip#441)
This PR wants to fix an issue about cancelation of listening socket. You can see the error on this CI output:
https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/661b80c8d56556cd711fb2e8f7a1c0edae56bf15
I would like to have a review to incorporate it into
6.1.0and it should close the issue #437. (/cc @talex5 & @hannesm)