Hey there. We’re seeing this issue sporadically across instances that are running badger3. Was there ever any fix for this? Essentially what happens is the database becomes corrupted and outputs this error when we try to read from it to debug. Can provide more information if needed, plus a badgerdb directory that produces this error reliably when one tries to read from it.