Get TransactionInfo size not eq

[polaz]

tried to setup mongodb event plugin ver 2.0 (2.2.1)
tron version 4.8.0

event.subscribe.version = 1
event.subscribe.startSyncBlockNum = <block_height>

got only first 341 blocks then

16:32:44.947 INFO  [history-event] [event](SolidEventService.java:70) Flush solid event Num:339,ID:0000000000000153d50f9a6dbc0f32d415719b7e1a75931d8435c6b54b70654c
16:32:44.948 INFO  [history-event] [event](RealtimeEventService.java:73) Flush realtime event Num:340,ID:0000000000000154593d5707420076c3cc6ffb8416aef9892be84a8a1da34426
16:32:44.948 INFO  [history-event] [event](SolidEventService.java:70) Flush solid event Num:340,ID:0000000000000154593d5707420076c3cc6ffb8416aef9892be84a8a1da34426
16:32:44.948 INFO  [history-event] [event](RealtimeEventService.java:73) Flush realtime event Num:341,ID:00000000000001554dc2e18a184605d848f0df73cf4482986b27c29414379a25
16:32:44.948 INFO  [history-event] [event](SolidEventService.java:70) Flush solid event Num:341,ID:00000000000001554dc2e18a184605d848f0df73cf4482986b27c29414379a25
16:32:44.948 ERROR [history-event] [event](BlockEventGet.java:348) Get TransactionInfo size not eq, blockNum 342, 1, 0
16:32:44.952 ERROR [history-event] [event](HistoryEventService.java:75) History event service fail.
java.lang.NullPointerException: null
	at org.tron.core.services.event.BlockEventGet.getContractTrigger(BlockEventGet.java:102)
	at org.tron.core.services.event.BlockEventGet.getBlockEvent(BlockEventGet.java:78)
	at org.tron.core.services.event.HistoryEventService.syncEvent(HistoryEventService.java:64)
	at org.tron.core.services.event.HistoryEventService.lambda$init$0(HistoryEventService.java:40)
	at java.lang.Thread.run(Thread.java:750)

if i manually set to go from event.subscribe.startSyncBlockNum = 342 it continues to block 1045 and fails there, then fails at block 1414 and so on

chain was downloaded from official mirror, stored on zfs with lz4 comp (if that matters) and synced to current state

[xxo1shine]

@polaz When the code was first launched, the transactionInfo information was not saved. If you want to synchronize events from the genesis block, you can deploy a new node and synchronize block from the genesis block.

[polaz]

Thanks for your clarification, i already noted that starting sync handles block 342 and so on

I dont know but in my opinion history-event errors should be either

• handled at the code level without stopping (maybe with some option like "skip-empty-blocks")
  or
• documented in some way - which block is safe to start from for history-event sync

best of all worlds is block re-sync (which can also help corrupted blockchains) but i understand that it is a huge effort to main codebase

[xxo1shine]

@polaz Thank you for your suggestion. Currently, the event service does not provide too many options. It cares more about data consistency. When encountering inconsistent data, the service will be stopped to avoid confusion or loss to users.

Considering that everyone's demands are different, perhaps multiple options can be configured for users to use, such as skipping or stopping the service when a block data cannot be loaded.