Patrick Lussan

I know it's not ideal but for people using docker I've built the image on my M1 and it's [available here](https://hub.docker.com/layers/200014581/lussanp/pgloader/latest/images/sha256-dd35daec515f28f15f9f094290aaf57b6fac37d69827776670866c734187b403?context=repo)

Do any of you use a failover strategy for their subscription (to handle socket timeouts for example) which tries to unsub/resub agressivelly? If so I think it could be the...

I found the same thing. the timeout URL was a concatenation of the hostname and a resolved IP: > "com.amazonaws.deepdish.http.HttpRequestException: io.netty.channel.ConnectTimeoutException: connection timed out: foo.bar.eu-west-3.elb.amazonaws.com/:4000" switching back to port 80...

Can confirm solution above works fine.

I've noticed it depends on the origin, it works on my S3 urls but not cloudfront for example.

I'm not familiar with GIT yet so here is the fix for anyone who encounters the issue: ``` @Override public boolean onInterceptTouchEvent(final MotionEvent ev) { final int action = ev.getAction();...

Can you try the following: ``` const _refetch = useCallback(() => { const task = InteractionManager.runAfterInteractions(async () => { if (refetch) await refetch() }) return () => task.cancel() }, [refetch])...

I've just tried in a fresh Yarn 2 (PNP) monorepo project and it works. ``` yarn --version 2.4.2 ``` `yarn run commitlint --edit "$1" `

sure, here is a trimmed copy: https://github.com/plus-/yarn-commitlint-sample

Possibly related to phantomjs issue https://github.com/facebook/react/pull/347