Kepler Airdrop not reporting status

I’ve been checking my logs and my coordinator does not appear to be reporting the status of the Kepler Airdrop project. It is in sync and all other projects are being updated - just this one is being singled out for some reason. I’ve restarted indexing the project with no joy and I’ve upgraded and restarted the coordinator with the same result. Any ideas on what the problem could be?

2023-06-30T07:25:47.968Z <transaction> INFO report project status: PROCESSING | project QmZGAZQ7e1oZgfu | block height: 16191030 | mmrRoot: 0x9e9b435dc74950a6ce1a4fe3687a74d467fe9304d954aba9cf11c2cf0001c1df 
2023-06-30T07:26:16.162Z <transaction> INFO report project status: SUCCEED 
2023-06-30T07:26:16.162Z <transaction> INFO report project status: PROCESSING | project QmQtmsHoJEYUcxK | block height: 2997302 | mmrRoot: 0xab017fbf93c0d7809544c645552760ef64e51b824730cf8a37ad7797bac8c0a2 
2023-06-30T07:26:44.163Z <transaction> INFO report project status: SUCCEED 
2023-06-30T07:26:44.163Z <transaction> INFO report project status: PROCESSING | project Qma5ytpgnpqvrgx | block height: 44507649 | mmrRoot: 0xf06c4f3c6bf92387f005412ba6ee7d2863df54f8397a129e790349fe92383ab3 
2023-06-30T07:27:20.190Z <transaction> INFO report project status: SUCCEED 
2023-06-30T07:27:20.190Z <transaction> INFO report project status: PROCESSING | project QmXwfCF8858YY92 | block height: 18580238 | mmrRoot: 0x897de019bb46c2878d54900417932b43b308b5a73b963bc585f950bb9f83beb8 
2023-06-30T07:27:48.150Z <transaction> INFO report project status: SUCCEED 
2023-06-30T08:00:00.759Z <transaction> INFO report project status: PROCESSING | project QmXwfCF8858YY92 | block height: 18580580 | mmrRoot: 0x0943d90de311971eba14862a1fd9f8831da6586c98c4053e6ac3554e88678ecf 
2023-06-30T08:00:01.100Z <transaction> WARN report project status: RETRY | project QmXwfCF8858YY92 | block height: 18580580 | mmrRoot: 0x0943d90de311971eba14862a1fd9f8831da6586c98c4053e6ac3554e88678ecf 
2023-06-30T08:00:01.100Z <transaction> INFO report project status: PROCESSING | project QmXwfCF8858YY92 | block height: 18580580 | mmrRoot: 0x0943d90de311971eba14862a1fd9f8831da6586c98c4053e6ac3554e88678ecf 
2023-06-30T08:01:32.385Z <transaction> INFO report project status: SUCCEED 
2023-06-30T08:01:32.385Z <transaction> INFO report project status: PROCESSING | project Qma5ytpgnpqvrgx | block height: 44508398 | mmrRoot: 0xd7e671d9ec1d7de84151298d2679b80c421c174ac67830bc5e727178b30be398 
2023-06-30T08:02:04.388Z <transaction> INFO report project status: SUCCEED 
2023-06-30T08:02:04.388Z <transaction> INFO report project status: PROCESSING | project QmQtmsHoJEYUcxK | block height: 2997439 | mmrRoot: 0x6533a3423dda2a19030095e34b06d98d3b62ff3da9cad0384fabc91d0b3fa661 
2023-06-30T08:02:32.434Z <transaction> INFO report project status: SUCCEED 
2023-06-30T08:02:32.434Z <transaction> INFO report project status: PROCESSING | project QmZGAZQ7e1oZgfu | block height: 16191370 | mmrRoot: 0x771a7f871752121596ef59e50157dcbb75fcada2b62eeebde12da486c1a9631e 
2023-06-30T08:03:12.419Z <transaction> INFO report project status: SUCCEED

You can see above we have wrapped back to reporting QmZGAZQ7e1oZgfu at the end without reporting on QmUwTD5dqQRRFcM.

I just went to get more recent logs and have found this:

2023-07-18T01:19:57.510Z <transaction> INFO report project status: PROCESSING | project QmZGAZQ7e1oZgfu | block height: 16446364 | mmrRoot: 0xc444a1e290c6621eb27187fcc8678a68eeafe19c00c3e569e0aad27a2c8cf459 
/usr/src/app/node_modules/@ethersproject/logger/lib/index.js:247
        throw this.makeError(message, code, params);
        ^

Error: overflow [ See: https://links.ethers.org/v5-errors-NUMERIC_FAULT-overflow ] (fault="overflow", operation="toNumber", value="100000000000000000", code=NUMERIC_FAULT, version=bignumber/5.7.0)
    at Logger.makeError (/usr/src/app/node_modules/@ethersproject/logger/lib/index.js:238:21)
    at Logger.throwError (/usr/src/app/node_modules/@ethersproject/logger/lib/index.js:247:20)
    at throwFault (/usr/src/app/node_modules/@ethersproject/bignumber/lib/bignumber.js:303:19)
    at BigNumber.toNumber (/usr/src/app/node_modules/@ethersproject/bignumber/lib/bignumber.js:151:13)
    at FragmentRunningEvent.<anonymous> (/usr/src/app/dist/payg/payg.sync.service.js:81:77)
    at Timeout._onTimeout (/usr/src/app/node_modules/@ethersproject/contracts/lib/index.js:502:31)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  reason: 'overflow',
  code: 'NUMERIC_FAULT',
  fault: 'overflow',
  operation: 'toNumber',
  value: '100000000000000000'
}

Which appears to be happening for Moonbeam Dictionary too:

2023-07-19T00:03:23.939Z <transaction> INFO report project status: PROCESSING | project QmeeqBHdVu7iYnh | block height: 4023196 | mmrRoot: 0x3bcfe5acb45ad5dc9f472cbbfa8a796184724a7356afbf18feed408e6beb36b3 
/usr/src/app/node_modules/@ethersproject/logger/lib/index.js:247
        throw this.makeError(message, code, params);
        ^

Error: overflow [ See: https://links.ethers.org/v5-errors-NUMERIC_FAULT-overflow ] (fault="overflow", operation="toNumber", value="100000000000000000", code=NUMERIC_FAULT, version=bignumber/5.7.0)
    at Logger.makeError (/usr/src/app/node_modules/@ethersproject/logger/lib/index.js:238:21)
    at Logger.throwError (/usr/src/app/node_modules/@ethersproject/logger/lib/index.js:247:20)
    at throwFault (/usr/src/app/node_modules/@ethersproject/bignumber/lib/bignumber.js:303:19)
    at BigNumber.toNumber (/usr/src/app/node_modules/@ethersproject/bignumber/lib/bignumber.js:151:13)
    at FragmentRunningEvent.<anonymous> (/usr/src/app/dist/payg/payg.sync.service.js:81:77)
    at Timeout._onTimeout (/usr/src/app/node_modules/@ethersproject/contracts/lib/index.js:502:31)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  reason: 'overflow',
  code: 'NUMERIC_FAULT',
  fault: 'overflow',
  operation: 'toNumber',
  value: '100000000000000000'
}

So maybe the initial issue (project not reporting at all) has been replaced with this problem where an error is being thrown. This is possible as the coordinator has been upgraded at least once since my original report.

Numeric overflow? Could a number have grown too big for the datatype being used to store it?

3 Likes