Reorg leads to JSON parse runtime error

[tk-o]

I noticed indexer app crash following an attempted reorg. There's very little information about the JSON object value itself, but I assume it'd be ENS resolver update including twitter handle.

How can I debug this issue further?

Context

Ponder version

v0.9.2

Relevant links:

• Indexing error after handling detected network fork namehash/ensnode#217

Error log

9:15:57 AM WARN  database   Failed 'revert' database method after '10' attempts (id=66295ba5)
error: invalid input syntax for type json
    at /app/node_modules/.pnpm/[email protected]/node_modules/pg/lib/client.js:526:17
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at PostgresConnection.executeQuery (file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:69:28)
    at PostgresConnection.connection.executeQuery (file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/driver/runtime-driver.js:89:24)
    at file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/query-executor/query-executor-base.js:35:28
    at SingleConnectionProvider.#run (file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/driver/single-connection-provider.js:25:16)
    at PostgresConnection.executeQuery (file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:88:41)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at PostgresConnection.connection.executeQuery (file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/driver/runtime-driver.js:89:24)
    at file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/query-executor/query-executor-base.js:35:28
    at SingleConnectionProvider.#run (file:///app/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/esm/driver/singleconnection-provider.js:25:16)
where: JSON data, line 1: {"com.twitter",...
unnamed portal parameter $6 = '...'
9:15:57 AM ERROR process    Caught unhandledRejection event
error: invalid input syntax for type json
    at file:///app/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected]_viem@_2zi2ugd7djddbbngl4rnlijcfu/node_modules/common/src/queue.ts:184:15
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
where: JSON data, line 1: {"com.twitter",...
unnamed portal parameter $6 = '...'
9:15:57 AM WARN  process    Received unhandledRejection, starting shutdown sequence

[kyscott18]

Is this the column that you suspect is causing the issue https://github.com/namehash/ensnode/blob/ba42018d4bda8af446f1438f925ebde521d1c126/packages/ponder-schema/src/ponder.schema.ts#L106 ?

[tk-o]

Hey @kyscott18, thank you for a quick reply 🙃

It's very likely that's the one, yes.

[tk-o]

I updated to ponder v0.9.10 and changed the schema:

https://github.com/namehash/ensnode/blob/c119d06/packages/ponder-schema/src/ponder.schema.ts#L119-L121

I'll report back once indexing reaches realtime phase and some forks were handled without the JSON parse error.