Frederik Schöll

Okay so trxdb-loader is up to date running live. We have 3 blockmeta instances running (on 3 different machines). On each machine there's a relayer running and blockmeta connects to...

Relayer seems fine: `head_block_time_drift{app="relayer"} -0.255444047` ``` $ grpcurl -plaintext -d '{"source":0}' localhost:9000 dfuse.headinfo.v1.HeadInfo/GetHeadInfo { "libNum": "32589425", "headNum": "32589755", "headID": "01f147bb72fa6bb4977a00062bab7b911394e733771a3c40b6d0d467f17f1f7b", "headTime": "2020-08-26T13:23:32.500Z" } ``` Blockmeta seems to be up-to-date as...

That's the debug output from abicodec: ``` Aug 26 13:45:11 jungle-abic11 dfuseeos[16142]: 2020-08-26T13:45:11.967Z (abicodec) starting ABI syncer (abicodec/syncer.go:81) Aug 26 13:45:11 jungle-abic11 dfuseeos[16142]: 2020-08-26T13:45:11.968Z (abicodec) streaming abi changes (abicodec/syncer.go:100){"cursor": "1:30352948:01cf2634aee0cc387c1631d68b66f56de0775d3745ee45ce983086d1a6f2c3b9:"}...

Is this the block id: `01cf2634aee0cc387c1631d68b66f56de0775d3745ee45ce983086d1a6f2c3b9` ? Then we have a fork, it's different that the one of block 30352948 from blocks: https://jungle.bloks.io/block/30352948

Updated Python to 3.12, but I'm getting this issue (tried updating PyYAML to 6.0.1 as well), has anybody an idea what causes this: ``` ==> python3 -c import setuptools... --no-user-cfg...

Unfortunately I won't be able to help you. Tried updating some dependencies but that just created new issues. I moved to a Linux VM as I just needed this client...

added a workaround for this in #1736 which proxies requests for now until we have a better and ideally decentralised solution