Follower and following names validation and type check
Mimic original behaviour:
- if following name does not exist do not process it: basically equal to drop op for single following entry
- if follower name does not exist drop op
- Mock data with different complex types combinations as names
Edited by Dariusz Kędzierski
Merge request reports
Activity
added 1 commit
- 09d5c94c - Follower and following entries must be strings. Same behaviour as in old hivemind
- Resolved by Dariusz Kędzierski
Does not match original behavior where follower attribute value has been interprated as string or operation has been rejected as is. See reference place where check has been done: https://gitlab.syncad.com/hive/hivemind/-/blob/master/hive/indexer/follow.py#L103 and definition of called 'Account.exist' method: https://gitlab.syncad.com/hive/hivemind/-/blob/master/hive/indexer/accounts.py#L68 There shall be also added tests to explicitly show follow changes on some testing account, when ops were accepted or not.
added To Do label
added 1 commit
- 6c22a3c4 - Mimic old hivemind behaviour for follower, following check. Use get_follow_count for testing
added 1 commit
- d376dabf - Hardcode 5000017 for max block to actually sync mocked data
added 1 commit
- dbef3168 - Revert exists method to its original form. List check is not needed there
added 11 commits
-
97e50698...8d06d8bc - 10 commits from branch
develop
- 51882997 - Rebase to current develop
-
97e50698...8d06d8bc - 10 commits from branch
- Resolved by Bartek Wrona
- Resolved by Dariusz Kędzierski
added 1 commit
- 31e5c984 - Removed delta calculations from follow.py. Follower/following calculation...
added 1 commit
- ddf50cf3 - Adding block number to follow update operation caused chages in notification patters.
added 4 commits
-
ddf50cf3...13868a13 - 3 commits from branch
develop
- 9db7c6b2 - Rebase to current develop
-
ddf50cf3...13868a13 - 3 commits from branch
Please register or sign in to reply