Incident: API down about daimo HOT 3 CLOSED

Culprit Shovel row

Unclear why this is null, current best guesses:

1. Fetched from Alchemy, maybe alchemy returned bad data?
2. Some panics around the fetching, could be related

from daimo.

Fixes

• #1161 , handle NULLs in shovel logs
• Shovel upgrade requested > adding non-nullable column support soon
• Add PagerDuty
• Migrate shovel DB, make columns non-nullable requires Shovel code update

As a follow up, we could also add typing to our SQL via eg. Prisma or TypeSQL. In this case, this would've replaced the any in function rowToRequestCreatedLog(r: any), and we would've caught that required columns like metadata were actually nullable.

from daimo.

Cause request transaction: https://basescan.org/tx/0xe08e8dc1f62566f8f0e0ce0289ba5fd41cfc555ec61afe73eccf54db6540be0c

from daimo.