Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove PersistableNetworkPayloadList & TradeStatisticsList #4159

Merged

Conversation

stejbac
Copy link
Contributor

@stejbac stejbac commented Apr 11, 2020

This is another refactoring PR to continue from the work in #4025, by removing PersistableNetworkPayloadList as suggested in the review. This together with #4102 removes all the remaining unnecessary PersistableEnvelope implementations.

This class is dead code, together with its store service, as they were only referenced from CorePersistenceProtoResolver::fromProto, the binding logic and from AppendOnlyDataStoreService by orphaned migration code. However, migration from the old persisted data was completed long ago and the store file is no longer being read or written from anywhere in the codebase.

Also remove its associated PersistableEnvelope proto message type, along with the TradeStatisticsList message type. The latter is long deprecated and has no corresponding Java class implementing PersistableEnvelope, so removing it won't change behaviour (outside the exception message thrown when attempting to resolve it).

The former class is dead code, together with its store service, as they
were only referenced from CorePersistenceProtoResolver::fromProto, the
binding logic and from AppendOnlyDataStoreService by orphaned migration
code. However, migration from the old persisted data was completed long
ago and the store file is no longer being read or written from anywhere
in the codebase.

Also remove the associated PersistableEnvelope proto message type, along
with the TradeStatisticsList message type. The latter is long deprecated
and has no corresponding Java class implementing PersistableEnvelope, so
removing it won't change behaviour (outside the exception message thrown
when attempting to resolve it).
@ripcurlx ripcurlx added the is:priority PR or issue marked with this label is up for compensation label Apr 13, 2020
@ripcurlx ripcurlx added this to the v1.3.3 milestone Apr 13, 2020
@ripcurlx ripcurlx requested a review from freimair April 28, 2020 14:27
Copy link
Contributor

@freimair freimair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • reviewed the code. nothing surpising there.
  • compiled and ran it, no surprises there either
  • started a mainnet client, no previously unseen exceptions
  • be aware that I only did a limited smoke test
  • but it looks good overall

its an ACK from me

Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:priority PR or issue marked with this label is up for compensation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants