You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2019. It is now read-only.
Sometimes when existing instance (ctrl+c) and we restart, gnarly will fail to apply ERC20 reducer patches.
I suspect this is due to 2 extra operations within the ERC20 reducer, my tests show that if I have only one extra operation it will not have this issue.
Recreate issue
I recreate it by randomly stopping the server and rebooting (with resuming on), once I recreate the issue, then every boot will fail.
ctrl-c that caused the bug:
equelize:pool connection acquired +0ms
sequelize:sql:pg executing(default) : UPDATE "erc20_balances" SET "balanceStr"='3149499999999999999',"patchId"='78525b54-177e-4373-9494-16c037a19559',"updatedAt"='2018-08-09 10:38:06.083 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x4969358e80cdC3D74477D7447BFfA3B2e2aCbe92' +1ms
sequelize:sql:pg executing(default) : UPDATE "erc20_balances" SET "balance"='3149499999999999999',"patchId"='78525b54-177e-4373-9494-16c037a19559',"updatedAt"='2018-08-09 10:38:06.085 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x4969358e80cdC3D74477D7447BFfA3B2e2aCbe92' +1ms
sequelize:sql:pg executed(default) : UPDATE "erc20_balances" SET "balance"='174199399999999999999',"patchId"='a4821b9b-81f7-4c48-97a2-c526281845a8',"updatedAt"='2018-08-09 10:38:06.068 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x4969358e80cdC3D74477D7447BFfA3B2e2aCbe92' +0ms
sequelize:pool connection released +1ms
sequelize:sql:pg executed(default) : UPDATE "erc20_balances" SET "balance"='1482159000000000000000',"patchId"='78525b54-177e-4373-9494-16c037a19559',"updatedAt"='2018-08-09 10:38:06.073 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x1Fc73344279F4D402Bb6eB3f41FD212013b7810c' +1ms
sequelize:sql:pg executed(default) : UPDATE "erc20_balances" SET "balance"='-171759999999999999999',"patchId"='a4821b9b-81f7-4c48-97a2-c526281845a8',"updatedAt"='2018-08-09 10:38:06.071 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x0bcd6ed54Df75d2BD2876C2900dfCcB2CA6F848e' +0ms
sequelize:pool connection released +1ms
sequelize:pool connection released +0ms
sequelize:sql:pg executed(default) : UPDATE "erc20_balances" SET "balanceStr"='3149499999999999999',"patchId"='78525b54-177e-4373-9494-16c037a19559',"updatedAt"='2018-08-09 10:38:06.083 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x4969358e80cdC3D74477D7447BFfA3B2e2aCbe92' +1ms
sequelize:pool connection released +1ms
sequelize:sql:pg executed(default) : UPDATE "erc20_balances" SET "balance"='3149499999999999999',"patchId"='78525b54-177e-4373-9494-16c037a19559',"updatedAt"='2018-08-09 10:38:06.085 +00:00' WHERE "id" = '0xe41d2489571d322189246dafa5ebde1f4699f498-0x4969358e80cdC3D74477D7447BFfA3B2e2aCbe92' +2ms
sequelize:pool connection released +2ms
sequelize:pool connection acquired +116ms
sequelize:sql:pg executing(default) : INSERT INTO "transactions" ("id","blockHash","createdAt","updatedAt","reducerId") VALUES ('6e8c01d0-599e-478c-b850-800c3d91f90a','0xb2a7ca9d945d4b2b00eac3ba9ae14088d61615aa6430d2226e4518c3e58e5da7','2018-08-09 10:38:06.219 +00:00','2018-08-09 10:38:06.219 +00:00','events') RETURNING *; +116ms
sequelize:sql:pg executed(default) : INSERT INTO "transactions" ("id","blockHash","createdAt","updatedAt","reducerId") VALUES ('6e8c01d0-599e-478c-b850-800c3d91f90a','0xb2a7ca9d945d4b2b00eac3ba9ae14088d61615aa6430d2226e4518c3e58e5da7','2018-08-09 10:38:06.219 +00:00','2018-08-09 10:38:06.219 +00:00','events') RETURNING *; +3ms
sequelize:pool connection released +4ms
gnarly-core:ourbit:events:notifyPatches txId: 6e8c01d0-599e-478c-b850-800c3d91f90a, patches: [] +3s
gnarly-core:api [getBlockByNumber] 5547564 0x54a62c +1s
gnarly-core:api [getBlockByNumber] 5547565 0x54a62d +186ms
gnarly-core:api [getBlockByNumber] 5547565 0x54a62d +45ms
^C gnarly Gracefully exiting. Send the signal again to force exit. +0ms
gnarly-core Gracefully decomposing reducers... +47s
gnarly-core:blockstream Pending Transactions: 0 +44s
gnarly-core:blockstream Pending Transactions: 0 +0ms
gnarly-core:blockstream Pending Transactions: 0 +0ms
gnarly-core:blockstream Pending Transactions: 0 +0ms
gnarly-core:blockstream Done! Exiting... +1ms
gnarly-core:blockstream Done! Exiting... +0ms
gnarly-core:blockstream Done! Exiting... +0ms
gnarly-core:blockstream Done! Exiting... +0ms
probably the best way to go about this is to implement unit tests because debugging it is really hard atm, also it might have been that I didnt get the error when I was using one operation because I was lucky, so don't let that distract you from exploring other reasons
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue
Sometimes when existing instance (ctrl+c) and we restart, gnarly will fail to apply ERC20 reducer patches.
I suspect this is due to 2 extra operations within the ERC20 reducer, my tests show that if I have only one extra operation it will not have this issue.
Recreate issue
I recreate it by randomly stopping the server and rebooting (with resuming on), once I recreate the issue, then every boot will fail.
ctrl-c that caused the bug:
reboot logs:
The text was updated successfully, but these errors were encountered: