fix: race condition in last processed height #38
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Error
https://babylonlabsworkspace.slack.com/archives/G07EDCXTXHR/p1731311842336389?thread_ts=1731302004.980249&cid=G07EDCXTXHR
Currently we have a main goroutine which consumes the events from channel and a separate go routine which parses the Babylon blocks and pushes these events to channel and then immediately updates last processed height.
If there is any issue in processing events, the last processed will point to a different height (as the go routine doesn't care if the event was successfully processed)
Fix - I removed the bbn event processor goroutine, its better to process events and then update ast processed height in th same routine to make sure all events at specific height are processed successfully.