Matt Mastracci

The signal is actually aborted regardless of success/error, so the example is not quite right.

Corrected example: ``` // server.ts Deno.serve(async (request) => { let operation, completed; request.signal.addEventListener('abort', () => { if (!completed) { console.log('Request was aborted by the client'); clearTimeout(operation); } }); return new...

I think it would look something like this: ``` req.onabort = () => { console.log("Request was aborted by the client"); }; // do something req.onabort = undefined; return new Response({...

This may be related to https://github.com/denoland/deno/issues/21749 as well.

Could you run: `openssl s_client -connect localhost:1433` ... and paste the output here? It may be that the underlying cipher supported by the DB engine is not supported by our...

It looks like the TLS cipher should be supported -- I will make sure that we correctly enable it for our tls library.

@massalinux Could you run this from Deno 1.38.2, but using the address of your database? ``` let hostname = 'HOSTNAME'; let port = PORT_NUMBER; let conn = await Deno.connectTls({hostname, port});...

Hmm. It looks like the server is not running or is not accessible. Is the docker container running? Can you access it any other way? You maybe need to use...

We may be able to better integrate the v8 profiler to remove a lot of the required steps to get a profiling trace.

Could you submit the contents of your /proc/cpuinfo? I have a theory it's a memory protection keys issue.