Philip Dubé
Philip Dubé
Guessing this would involve having an async task in background keeping connection alive
Didn't mean as workaround, but in consideration for what clickhouse-rs should be doing to get around this issue
I'm probably mistaken then @FireMasterK are you using direct connection to clickhouse? ie no private link or ssh tunnel or http load balancer involved
https://github.com/jackc/pgx/issues/2086
waiting on https://github.com/tremorlabs/tremor-npm/pull/1151
#3634
(note that modern go.uber.org/atomic uses these atomic types, their String is specialization built on top of Value which is takes `interface{}` for Load/Store) https://github.com/uber-go/atomic/blob/v1.11.0/string.go#L26 https://github.com/uber-go/atomic/blob/v1.11.0/value.go#L27
> This is optional dependency. So if some users prefer to use `data-encoding`, while others `base64`, may be we can keep both cases, and to call `panic!` at compile time,...
@davemilter it isn't a technical issue, not using base64 is rooted in disagreeing with maintainer's rude handling of a request to maintain simple api: https://github.com/marshallpierce/rust-base64/issues/213 Maybe an effort can be...
if we reenable this it'll probably be with eventhubs emulator