Nelson Vides
Nelson Vides
I've just tried to write a test for it. Will deploy this in my env in the next few days and will let you know, in the meantime please let...
@essen tested in my environments, I do get `{error, closed}` and logs aren't dirty with crashes.
> Please don't add a new test group and instead make the test against all http/https/h2/h2c instead so we know it's working for both TCP and TLS and all protocols....
Just pushed the test, it generally fails the https group with a timeout when waiting for the 'DOWN' message.
Right, the Pid that `ct_helper:get_remote_pid_tcp/1` is not the same than the socket is listening to, so it doesn't receive the `DOWN` message. This happens only for the `https` and `h2`...
> There's a separate function for TLS. Just saw that, but that won't work, because it's doing ssl:sockname, and this socket is not yet a ssl socket, it's a barebones...
@essen now, I've pushed a new version of the test that does a bit of a hack, hopefully elegant, to correctly find the process we want to track the dead...
@essen did you have a chance to review the latest changes? :)
> No but the tab is still open for whenever this can happen. Hi there, it's been a while, how's progress on this one? :)
@essen heads up on this, any updates, plans?