Mysterious Behavior in Logs in Recipts on Failed Transactions

Hi!

After reading through the indexer code, it seems like you only look for data logs, but completely ignore that the transaction panicked (in the decodeReceipt function). Note that transactions are atomic, meaning that a panicking transaction is completely reverted and e.g. storage writes do not cause any effects. In this case I suspect your code runs out of gas after emitting the logs, and the receipts support that conclusion.