In debug_node, current_feed_publication_time resets on reload

[vikramrajkumar]

From @theoreticalbts on March 16, 2016 7:14

I think this wasn't found because check_reflect.py might not be checking object classes.

Related: cryptonomex/graphene#615

Copied from original issue: cryptonomex/graphene#624

[vikramrajkumar]

From @theoreticalbts on March 16, 2016 14:7

Wait a minute, it is reflected after all lower down...but it is not loading properly for some reason.

Reproduction steps: Generate blocks, check 2.4.x, reload, check 2.4.x again, current_feed_publication_time is reset.

[vikramrajkumar]

From @theoreticalbts on March 16, 2016 14:29

NB this occurred on a chain consisting of BitShares, plus a week's worth of empty blocks produced by dbg_generate_blocks.

[pmconrad]

Tested with live data. current_feed_publication_time is saved/restored as expected.
The observed behaviour was either due to old code (a lot has changed since then), or due to the week of empty blocks which would expire all feeds.

[abitmore]

Probably fixed by cryptonomex/graphene#614 and cryptonomex/graphene#617. Anyway, I agree that we can close this issue.