inconsistent data presented by views for applications when micro forks happen and new irreversible block is set
Because hive.remove_obsolete_reversible_data removes reversible blocks data regardless of application states and forks which they are processing, the applications can see inconsistent state -> mix of blocks from abandoned forks and new irreversible blocks from fork currently in force. Problem presented on the picture: After a back from fork I, the application sees abandoned by hived block 4 from fork I, and irreversible block 3 from fork II instead of abandoned block 3 form fork I. A functional test which proofs the problem (the 'context' sees an abandoned block 9 from fork 2 and a block 8 from fork 3): set_irreversible_and_context_blocks_view_test.sql