fix duplicate inserts

[iuwqyir]

TL;DR

Replaced ticker with sleep interval in committer and added empty data check for block insertions

What changed?

• Replaced time.NewTicker with time.Sleep in the committer's main loop
• Added validation to prevent processing empty block data in InsertBlockData

How to test?

1. Run the test suite to verify committer functionality
2. Verify committer continues to process blocks at the specified interval
3. Test InsertBlockData with empty block data to ensure it handles the case gracefully

Why make this change?

Ticker will trigger on the nearest configured time tick. Meaning that if the interval is 1 second and loop finishes at 0.999, then the next loop will start in 1 millisecond.

This can create cases where the next committer loop reads the DB to get the latest block, but it hasn't propagated to all distributed DB machines yet and thus returns an old block and the loop will commit the same data as the last loop.

Using sleep will fix this because it will always wait the configured interval after the previous commit is done

[zeet-co]

We're building your pull request over on Zeet.
Click me for more info about your build and deployment.
Once built, this branch can be tested at: https://debug-xai-cbng-02-18-fix-duplicat-0aebce.insight-prod-gke.zeet.app before merging 😉

[iuwqyir]

• debug committer #153
• fix duplicate inserts #154 👈 (View in Graphite)
• improve token balances mv #152
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.