Chulki Lee

@wojtekmach updated the issue description with more tests. I found that it only happens when I talk to ProxySQL. If I run the query directly MySQL, it works. Interesting.. I...

I'm maintaining own formatter implementing Logger.Formatter... and here are my thoughts (with exciting Elixir 1.11 changes). * timestamp - should use `:microsecond`, not `:native` to match with [`:logger.timestamp/0`](https://erlang.org/doc/man/logger.html#timestamp-0) * Also.....

Since `event_name` and `measurement` are *required* and principal arguments here, I think it's better to move it to the top level arg, instead of making them as overridable from options....

If telemetry metrics struct is to capture all info for reporter, then what about moving reporter options to the top level argument? Or we may extract metrics opts and then...

Hm seems like I have the same problem with httpc ```elixir bad_url1 = "https://expired.badssl.com/" bad_url2 = "https://wrong.host.badssl.com/" # httpc # httpc by default does not check ssl {:ok, _} =...

If connection pool manager picks up previous connection with different connect opts, then that's bad behavior. (I don't think httpc has built-in pool manager correct me if I'm wrong) I...

Oh, I think the real issue is HTTP connection reuse. If I add `connection: close` HTTP header to explicit stop reusing HTTP connection, it works without `reuse_sessions` (as it always...

I did find those workarounds (already mentioned in the body). > you can control connections per pool. Meaning you can start one pool for insecure connections and another cor secured...

Thanks a lot for the input and the update! I think the naivest implementation is: dump ssl option into binary deterministic way (e.g. in elixir `"default_" inspect(ssloptions)`) and use it...

So the main issue here is: whether Jason should raise error, or return error tuple, for such invalid value. ```elixir Jason.encode(%{{:hello, 1} => 1}) ** (Protocol.UndefinedError) protocol String.Chars not implemented...