Kevin pfp

Kevin

@typedarray.eth

462 Following
158179 Followers


Kevin pfp
26 replies
87 recasts
493 reactions

Kevin pfp
8 replies
15 recasts
85 reactions

Kevin pfp
5 replies
12 recasts
40 reactions

Kevin pfp
7 replies
1 recast
38 reactions

Kevin pfp
1 reply
4 recasts
24 reactions

Kevin pfp
1 reply
0 recast
16 reactions

Kevin pfp
4 replies
5 recasts
29 reactions

Kevin pfp
5 replies
5 recasts
33 reactions

Kevin pfp
4 replies
7 recasts
42 reactions

Kevin pfp
2 replies
2 recasts
14 reactions

Kevin pfp
3 replies
3 recasts
28 reactions

Kevin pfp
6 replies
2 recasts
49 reactions

Kevin pfp
4 replies
3 recasts
34 reactions

Kevin pfp
2 replies
2 recasts
23 reactions

Kevin pfp
2 replies
7 recasts
47 reactions

Kevin pfp
21 replies
54 recasts
228 reactions

Kevin pfp
2 replies
0 recast
39 reactions

Kevin pfp
4 replies
1 recast
16 reactions

Kevin pfp
0 reply
0 recast
15 reactions

Kevin pfp
Fun debugging rabbit hole from this week. Last week, a few Ponder users opened issues for an "invalid byte sequence for encoding "UTF8": 0x00" error. Most software ignores or removes null characters (\0, \x00, or \u0000), but the Postgres TEXT data type rejects them with that error. We reproduced the issue with an ENS NameRegistered event log from 2022 (s/o @greg). Turns out, some EVM event logs contain null characters within decoded `string` parameter values. Now, the framework removes null characters from all decoded ABI parameters before passing them to userland. We could have instead fixed this on the PG driver/Drizzle side, but it seemed more fragile (are we wrong?). We're not certain why this only appeared recently - we haven't changed any relevant codepaths in recent releases. My best guess is that Viem used to remove them but stopped. Viem is a peer dep, so the version can change independently from Ponder's version. PR: https://github.com/ponder-sh/ponder/pull/1414
1 reply
5 recasts
26 reactions