FlushError & Unexpected data beyond EOF

[Clonescody]

Version

ponder 0.8.14

Current behavior

After upgrading to ponder 0.8.14 (from @ponder/core 0.7.17), running the indexer throws some errors & warnings before stopping.
A couple different errors happen, firstly, the table.flush() function fails when trying to flush cache. This happens after some events are read and indexed correctly

The second issue is an error thrown with regard to flushing as well FlushError: unexpected data beyond EOF in block 0 of relation base/1/47350

I am indexing datas on the Arbitrum chain, not sure what could help to debug feel free to ask for details.

Expected behavior

Indexing should run fully and db flush functions should run.

Steps to reproduce

The code can be found in this gist where I added the config, schema, indexing functions and ABIs

Link to repository

No response

Anything else?

No response

[typedarray]

Thanks for opening.

1. Does this happen consistently / reproducibly?
2. Where is this ponder app running?
3. Where is the Postgres server running? Local machine? Over a virtual/network file system perhaps? Quick searches indicate that this only happens on Postgres servers running over network file systems.

[Clonescody]

1. Yeah, tried to regen and reinstall but error remains the same, started happening for more tables after full reinstall

2. It's running on my local machine using pglite, all tables are created correctly, indexing starts and goes to 95%+ before stopping
3. Per above, everything running on my local machine ( mac Ventura 13 / node v20.14.0 / postgres 14.15 )

[Clonescody]

More details :

• I reverted my ponder to 0.7.17 for now, I had to delete the .ponder folder as the DB wasn't starting properly (probably due to 0.8 migration prior), and after doing this it works fine as it used to.
• Learning from the above I tried to go back to 0.8 and deleting the .ponder folder as well to see if a fresh install would work. No chance on that either, I got the same flush() error, but also a couple of new ones indicating that the schemas weren't setup correctly

Staying on 0.17 for now as that's what works for me, but can easily test 0.8 if you need me to 👍