j4$0n

Any update?

Meet the same issue on local development with docker, and the graph-node version is, > graph-node 0.23.1 (2021-06-23) ``` graph-node_1 | Aug 25 10:58:25.036 ERRO Subgraph instance failed to run:...

@leoyvens Everything works fine after updating the latest version. - @graphprotocol/graph-cli (0.33.0) - @graphprotocol/graph-ts (0.27.0) > docker pull graphprotocol/graph-node:latest And the latest `graph-node` in local also shows more specific trace...

@jbc-deve @voroncv are correct. from `connectors.ts`, we should configure the connector as a function if it is a new customized connector, ``` for (const [id, initOrConfig] of Object.entries(initsOrConfigs)) { //...

Same issue on the version - `2.59.0`. And the @Wunsz 's workaround is not working for me. ``` "@uniswap/widgets": "^2.59.0", "react": "^18.3.1", "react-dom": "^18.3.1", "react-redux": "^9.1.2", "react-scripts": "5.0.1", "typescript": "^4.4.2",...

Agree. The `bigint` type should be represented as `String`.

Any update on `signet.ordinals.com`? Still, get the error - `Connection timed out Error code 522`.

This issue comes up occasionally... It will disappear if retry the login process. And here is the scopes, > { scope: ['tweet.read', 'users.read', 'offline.access'] } ``` 2024-01-05 02:02:08 | default...

Okay, it may be a rate limit issue. Logging the error, ```bash { 'x-rate-limit-limit': '1200000', 'x-rate-limit-reset': '1704706892', 'content-disposition': 'attachment; filename=json.json', 'x-content-type-options': 'nosniff', 'x-rate-limit-remaining': '1199994', 'strict-transport-security': 'max-age=631138519', 'x-user-limit-24hour-limit': '25', 'x-user-limit-24hour-reset': '1704786996',...

Same issue. The bad news is that commands like `gpg/wget/curl` are unavailable in my base image environment. My workaround is removing the repository before `apt-get update` to bypass the GPG...