Ning Sun

Once http-rs/http-client#74 merged we can simply upgrade async-std to 1.9 and use their `tokio1` feature to get surf work on tokio 1.0.

Sorry, let me check later today

It seems the main branch doesn't compile on wasm either, due to error from `getrandom`.

@Fishrock123 it compiles on all targets. However, because the `getrandom` dependency was introduced in `http-types`, I'm not sure if it's good to add target check here

@Fishrock123 I'm not quite sure if a feature flag could fix this. Could you please show me some detail about that?

We can make udf and script different objects in database. Stored procedure in snowflake: https://docs.snowflake.com/en/sql-reference/stored-procedures.html UDFs in snowflake: https://docs.snowflake.com/en/sql-reference/user-defined-functions.html

This EOF error happens quite frequently in our cloud deployment. It should be a bug in the protocol layer.

The error message `received corrupt message` is from [rustls](https://github.com/rustls/rustls/blob/v/0.20.8/rustls/src/error.rs#L149). According to its doc, this happens when the peer (client) is not talking tls protocol. I cannot reproduce this issue with...

In diehard, the last exception is thrown when retries exceeds: ```clj (testing "max retry" (is (thrown? clojure.lang.ExceptionInfo (with-retry {:max-retries 3} (throw (ex-info "expected" {})))))) ``` Perhaps this will work for...

I got your point. But using fallback for throwing this exception is a little hack because fallback is designed to provide a value. The throw exception, you have other ways...