Bug subsquid

Nodes Indexers
2

@HugoTrentesaux Voici les logs pertinents, du processor:

duniter-squid-processor-1     | {"level":2,"time":1720554246107,"ns":"sqd:processor","msg":"2169697 / 2169697, rate: 0 blocks/sec, mapping: 43 blocks/sec, 129 items/sec, eta: 0s"}
duniter-squid-processor-1     | {"level":2,"time":1720554252211,"ns":"sqd:processor","msg":"2169698 / 2169698, rate: 0 blocks/sec, mapping: 43 blocks/sec, 130 items/sec, eta: 0s"}
duniter-squid-processor-1     | {"level":2,"time":1720554264256,"ns":"sqd:processor","msg":"2169699 / 2169699, rate: 0 blocks/sec, mapping: 31 blocks/sec, 93 items/sec, eta: 0s"}
duniter-squid-processor-1     | {"level":2,"time":1720554708561,"ns":"sqd:processor","msg":"2169707 / 2169707, rate: 0 blocks/sec, mapping: 25 blocks/sec, 75 items/sec, eta: 0s"}
duniter-squid-processor-1     | {"level":5,"time":1720554708768,"ns":"sqd:processor","err":{"generatedMessage":true,"code":"ERR_ASSERTION","actual":false,"expected":true,"operator":"==","stack":"AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:\n\n  (0, assert_1.default)(head.height >= this.chain[0].height)\n\n    at HotProcessor.moveToBlocks (/squid/node_modules/@subsquid/util-internal-ingest-tools/lib/hot.js:60:30)\n    at HotProcessor.goto (/squid/node_modules/@subsquid/util-internal-ingest-tools/lib/hot.js:38:24)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async RpcDataSource.handleNewHeads (/squid/node_modules/@subsquid/substrate-data-raw/lib/datasource.js:213:24)\n    at async RpcDataSource.subscription (/squid/node_modules/@subsquid/substrate-data-raw/lib/datasource.js:198:25)\n    at async RpcDataSource.processHotBlocks (/squid/node_modules/@subsquid/substrate-data-raw/lib/datasource.js:113:13)"}}

Ce sont les dernier logs du processor, rien après.
Zoom sur l’erreur:

{
    "generatedMessage": true,
    "code": "ERR_ASSERTION",
    "actual": false,
    "expected": true,
    "operator": "==",
    "stack": "AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:\n\n" +
             "  (0, assert_1.default)(head.height >= this.chain[0].height)\n\n" +
             "    at HotProcessor.moveToBlocks (/squid/node_modules/@subsquid/util-internal-ingest-tools/lib/hot.js:60:30)\n" +
             "    at HotProcessor.goto (/squid/node_modules/@subsquid/util-internal-ingest-tools/lib/hot.js:38:24)\n" +
             "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n" +
             "    at async RpcDataSource.handleNewHeads (/squid/node_modules/@subsquid/substrate-data-raw/lib/datasource.js:213:24)\n" +
             "    at async RpcDataSource.subscription (/squid/node_modules/@subsquid/substrate-data-raw/lib/datasource.js:198:25)\n" +
             "    at async RpcDataSource.processHotBlocks (/squid/node_modules/@subsquid/substrate-data-raw/lib/datasource.js:113:13)"
}

On remarque qu’il traite les block les un à la suite des autres, jusqu’au block 2169699 où il saute directement au block 2169707.

Issue déjà ouverte par moi même à ce sujet, fermé depuis mais tu constatera dans les commentaires que j’avais bien sentie que ça avait été fermé un peu au pif:

La dernière fois c’était 9 block de sautés, cette fois ci 8 block.
J’ai donc relancé @belopash sur ce sujet.

edit: qui m’a répondu en moins de 5 minutes: Processor crashed with missing blocks despite correct DB entries · Issue #253 · subsquid/squid-sdk · GitHub

Il utilise VSCode, cet homme a du goût.

Donc il faut mettre à jour squid.
cc @bgallois étant donné que je vois dans les commits que tu bosses sur squid en ce moment :slight_smile:

1 Like