Rollforward: Keep track of previously processed posts #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…. add test case to cover previous issue
bt-cryptomancer
approved these changes
Nov 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rollforward of #111 with fix.
Fixes interval adding all posts within range, and allows comments to paid out posts to be properly indexed, and does not allow comments to re-activate after payout.
Adds new table called 'postMetadata' that maps authorperm to rewardPoolIds. Can be extended to store more in the future if needed. Lookups are by primary key _id, should be efficient, and does not affect the index for posts for a given reward pool.
This also adds a node change to make it so that MongoErrors properly error out completely rather than allow the node to infinite loop.