Compression | Data Compression using Huffman | Compression library

Here I'm wondering about the line [in s_client]
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384

You're apparently using OpenSSL 1.0.2, where that's a basically useless relic. Back in the days when OpenSSL supported SSLv2 (mostly until 2010, although almost no one used it much after 2000), the ciphersuite values used for SSLv3 and up (including all TLS, but before 2014 OpenSSL didn't implement higher than TLS1.0) were structured differently than those used for SSLv2, so it was important to qualify the ciphersuite by the 'universe' it existed in. It has almost nothing to do with the protocol version actually used, which appears later in the session-param decode:

Mayby you are missing

How do I pull the upstream branch into my local? Every time I try it wants to merge

That's the definition of pull as delivered (with factory-default options): fetch and merge.

You just want to fetch. At the factory default settings,

As per comments, you can run:

For those who may run into same problem, problem was REDIS misconfiguration, after third deployment we carefully set parameters and no problem was found.

So that you can put a directory structure into a single file, which makes it possible to send it to someone or to save it. Then they or you can reconstruct the directory structure from that file.

You can call sp_estimate_data_compression_savings for each table, specifying the desired compression level. Below is an example script that uses a cursor for the task, inserting the results of each table into a table variable and the final results of all tables via a select query.

I notice that you're connecting to https://mydomain.dev, but passing a host header for a different domain. My guess would be that curl is sending an SNI request for a mydomain.dev cert; since networking-ns-cert will acquire wildcard certs for *..my domain.dev, it's possible that the server doesn't have a cert matching the SNI request, and closes the TCP connection.

Try using the -kvv options to curl (instead of -v) to print more verbose debugging information and bypass some SSL errors. Since you have DNS and certs set up, I'd try:

curl -kvv https://helloworld-go.default.mydomain.dev

The stream parameter of a new GZipStream is the destination stream. To process the input to the output, you need to write to the instance of GZipStream somehow.

When I experimented with it, I found that a call to csvWriter.FlushAsync() was necessary.

Like this: