Describe the bug
I want to connect to Redis Memory store in GCP and got the following error:

Error: Redis connection to <port> failed - unable to verify the first certificate at TLSSocket.onConnectSecure
(_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket._finishInit (_tls_wrap.js:937:8) at
TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12) 

*To Reproduce

The problem

The current implementation of processElement

1. Check if cache existence for input
2. If the cache returns value return it
3. otherwise, aquire a semaphore
4. call asyncLookup and pass it input. It return a future: F
5. Maintain a list of the currently executing futures
6. release a semaphore at the end each future execution
7. make sure all the future are com

Problem

At present Jitsu tracks, the only server starts/stops events and events from JS/API. We should improve telemetry for understanding how users use our product. There should be additional telemetry in the jitsucom/server as well as in jitsucom/configurarator frontend. We should understand:

• What types of sources/destinations are used;
• From what source to what destination event

The functions in this file should be factored out to a separate utility lib as they are reused in bitcoin-etl https://github.com/blockchain-etl/ethereum-etl/blob/develop/ethereumetl/misc_utils.py

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

• base.html - @tymosh
• base_chapter.html - @tymosh
• error.html - @tymosh

2020

• base.html - @tymosh
• contributors.html - @tymosh
• [x]

Over time we've had some things leak into the diff methods that make it more cumbersome to use BigDiffy via code instead of CLI.

For example diffAvro here https://github.com/spotify/ratatool/blob/master/ratatool-diffy/src/main/scala/com/spotify/ratatool/diffy/BigDiffy.scala#L284

User has to manually pass in schema otherwise we they receive a non-informative error regarding null schema, add

As far as I can tell, these functions are completely unused and can be removed:

• https://github.com/pydata/pandas-gbq/blob/9fb246469af2972db0052522f5000cdafee41b4c/tests/system/test_auth.py#L14
• https://github.com/pydata/pandas-gbq/blob/9fb246469af2972db0052522f5000cdafee41b4c/tests/system/test_auth.py#L39

@medvedev1088
Hi,
I found that there ara two kinds of output in transactions.json.
One is nonstandard, and the other is pubkeyhash.
I thought the nonstandard output is the op_return output, but i found outputs of many (not all ) coinbase txs also are nonstandard. And address of miner is like“nonstandard3318537dfb3135df9f3d950dbdf8a7ae68dd7c7d”.
Here is an example:
transaction: {
"hash":