blocks displayed in warp explorer and scan explorer are inconsistent

[drumfeet]

I think some transactions are not written to the WAL contract because If I fetch the blocks collection in the WAL contract, it does not return the most recent Warp transaction. I also observed that if I fetch the txs collection in the WAL contract that the most recent transactions does not have warp and block property.

[drumfeet]

I haven't had a test case yet coz this issue occurs very random. I have just observed this occurs when I make a write query to the node in sequence for a long time. Like a couple of thousand transactions, and then it probably stops writing the transaction to blocks collection.

[drumfeet]

I think it is during the batch query that it fails to write the most recent block in the WAL. I could not replicate it yet coz it happens randomly, but it is during call to await this.wal.batch(batch) in the bundle() function of rollup.js file