I'm trying to understand how I am failing to shut down an ssl-listener on v7.7.0.5.
https://gist.github.com/zyrolasting/bc5477bfa60d7185d0f53a5142545f88 shows my use of ssl-* procedures to transmit data using test.pem. The problem is that I cannot run the test submodule twice in a row because the listening port is still occupied on subsequent runs. I added ssl-close on top of a custodian shutdown and that problem reproduces. For comparison, https://gist.github.com/zyrolasting/3feb0ff4ecdf0b49bcf3e0ed8b630a06 avoids the ssl-* procedures and just uses vanilla TCP. I can run the tests fine then. But in looking at mzssl.rkt in the source, it looks like shutdown requires calling a foreign function via SSL_shutdown. https://github.com/racket/racket/blob/master/racket/collects/openssl/mzssl.rkt#L1417 Do I have to call ports->ssl-ports out of band just so closing them sends a shut down as a side-effect? Or is keeping the port occupied between test runs a bug? ~slg -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/EclLZhgUYlzvOx_uS0Ec154iNVVwXxNeZWcTIDzd72lwkA3M2OhVf8AW_cVMVUudM50kLuLVvnnnmiRGvZDvz5tPSUVOqFkC2LVI-2LY18Q%3D%40sagegerard.com.
