You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

263 lines
10 KiB

Non-Serial ("Snowflake") IDs (#4801) * Use non-serial IDs This change makes a number of nontrivial tweaks to the data model in Mastodon: * All IDs are now 8 byte integers (rather than mixed 4- and 8-byte) * IDs are now assigned as: * Top 6 bytes: millisecond-resolution time from epoch * Bottom 2 bytes: serial (within the millisecond) sequence number * See /lib/tasks/db.rake's `define_timestamp_id` for details, but note that the purpose of these changes is to make it difficult to determine the number of objects in a table from the ID of any object. * The Redis sorted set used for the feed will have values used to look up toots, rather than scores. This is almost always the same as the existing behavior, except in the case of boosted toots. This change was made because Redis stores scores as double-precision floats, which cannot store the new ID format exactly. Note that this doesn't cause problems with sorting/pagination, because ZREVRANGEBYSCORE sorts lexicographically when scores are tied. (This will still cause sorting issues when the ID gains a new significant digit, but that's extraordinarily uncommon.) Note a couple of tradeoffs have been made in this commit: * lib/tasks/db.rake is used to enforce many/most column constraints, because this commit seems likely to take a while to bring upstream. Enforcing a post-migrate hook is an easier way to maintain the code in the interim. * Boosted toots will appear in the timeline as many times as they have been boosted. This is a tradeoff due to the way the feed is saved in Redis at the moment, but will be handled by a future commit. This would effectively close Mastodon's #1059, as it is a snowflake-like system of generating IDs. However, given how involved the changes were simply within Mastodon, it may have unexpected interactions with some clients, if they store IDs as doubles (or as 4-byte integers). This was a problem that Twitter ran into with their "snowflake" transition, particularly in JavaScript clients that treated IDs as JS integers, rather than strings. It therefore would be useful to test these changes at least in the web interface and popular clients before pushing them to all users. * Fix JavaScript interface with long IDs Somewhat predictably, the JS interface handled IDs as numbers, which in JS are IEEE double-precision floats. This loses some precision when working with numbers as large as those generated by the new ID scheme, so we instead handle them here as strings. This is relatively simple, and doesn't appear to have caused any problems, but should definitely be tested more thoroughly than the built-in tests. Several days of use appear to support this working properly. BREAKING CHANGE: The major(!) change here is that IDs are now returned as strings by the REST endpoints, rather than as integers. In practice, relatively few changes were required to make the existing JS UI work with this change, but it will likely hit API clients pretty hard: it's an entirely different type to consume. (The one API client I tested, Tusky, handles this with no problems, however.) Twitter ran into this issue when introducing Snowflake IDs, and decided to instead introduce an `id_str` field in JSON responses. I have opted to *not* do that, and instead force all IDs to 64-bit integers represented by strings in one go. (I believe Twitter exacerbated their problem by rolling out the changes three times: once for statuses, once for DMs, and once for user IDs, as well as by leaving an integer ID value in JSON. As they said, "If you’re using the `id` field with JSON in a Javascript-related language, there is a very high likelihood that the integers will be silently munged by Javascript interpreters. In most cases, this will result in behavior such as being unable to load or delete a specific direct message, because the ID you're sending to the API is different than the actual identifier associated with the message." [1]) However, given that this is a significant change for API users, alternatives or a transition time may be appropriate. 1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html * Restructure feed pushes/unpushes This was necessary because the previous behavior used Redis zset scores to identify statuses, but those are IEEE double-precision floats, so we can't actually use them to identify all 64-bit IDs. However, it leaves the code in a much better state for refactoring reblog handling / coalescing. Feed-management code has been consolidated in FeedManager, including: * BatchedRemoveStatusService no longer directly manipulates feed zsets * RemoveStatusService no longer directly manipulates feed zsets * PrecomputeFeedService has moved its logic to FeedManager#populate_feed (PrecomputeFeedService largely made lots of calls to FeedManager, but didn't follow the normal adding-to-feed process.) This has the effect of unifying all of the feed push/unpush logic in FeedManager, making it much more tractable to update it in the future. Due to some additional checks that must be made during, for example, batch status removals, some Redis pipelining has been removed. It does not appear that this should cause significantly increased load, but if necessary, some optimizations are possible in batch cases. These were omitted in the pursuit of simplicity, but a batch_push and batch_unpush would be possible in the future. Tests were added to verify that pushes happen under expected conditions, and to verify reblog behavior (both on pushing and unpushing). In the case of unpushing, this includes testing behavior that currently leads to confusion such as Mastodon's #2817, but this codifies that the behavior is currently expected. * Rubocop fixes I could swear I made these changes already, but I must have lost them somewhere along the line. * Address review comments This addresses the first two comments from review of this feature: https://github.com/tootsuite/mastodon/pull/4801#discussion_r139336735 https://github.com/tootsuite/mastodon/pull/4801#discussion_r139336931 This adds an optional argument to FeedManager#key, the subtype of feed key to generate. It also tests to ensure that FeedManager's settings are such that reblogs won't be tracked forever. * Hardcode IdToBigints migration columns This addresses a comment during review: https://github.com/tootsuite/mastodon/pull/4801#discussion_r139337452 This means we'll need to make sure that all _id columns going forward are bigints, but that should happen automatically in most cases. * Additional fixes for stringified IDs in JSON These should be the last two. These were identified using eslint to try to identify any plain casts to JavaScript numbers. (Some such casts are legitimate, but these were not.) Adding the following to .eslintrc.yml will identify casts to numbers: ~~~ no-restricted-syntax: - warn - selector: UnaryExpression[operator='+'] > :not(Literal) message: Avoid the use of unary + - selector: CallExpression[callee.name='Number'] message: Casting with Number() may coerce string IDs to numbers ~~~ The remaining three casts appear legitimate: two casts to array indices, one in a server to turn an environment variable into a number. * Only implement timestamp IDs for Status IDs Per discussion in #4801, this is only being merged in for Status IDs at this point. We do this in a migration, as there is no longer use for a post-migration hook. We keep the initialization of the timestamp_id function as a Rake task, as it is also needed after db:schema:load (as db/schema.rb doesn't store Postgres functions). * Change internal streaming payloads to stringified IDs as well This is equivalent to 591a9af356faf2d5c7e66e3ec715502796c875cd from #5019, with an extra change for the addition to FeedManager#unpush. * Ensure we have a status_id_seq sequence Apparently this is not a given when specifying a custom ID function, so now we ensure it gets created. This uses the generic version of this function to more easily support adding additional tables with timestamp IDs in the future, although it would be possible to cut this down to a less generic version if necessary. It is only run during db:schema:load or the relevant migration, so the overhead is extraordinarily minimal. * Transition reblogs to new Redis format This provides a one-way migration to transition old Redis reblog entries into the new format, with a separate tracking entry for reblogs. It is not invertible because doing so could (if timestamp IDs are used) require a database query for each status in each users' feed, which is likely to be a significant toll on major instances. * Address review comments from @akihikodaki No functional changes. * Additional review changes * Heredoc cleanup * Run db:schema:load hooks for test in development This matches the behavior in Rails' ActiveRecord::Tasks::DatabaseTasks.each_current_configuration, which would otherwise break `rake db:setup` in development. It also moves some functionality out to a library, which will be a good place to put additional related functionality in the near future.
6 years ago
Account domain blocks (#2381) * Add <ostatus:conversation /> tag to Atom input/output Only uses ref attribute (not href) because href would be the alternate link that's always included also. Creates new conversation for every non-reply status. Carries over conversation for every reply. Keeps remote URIs verbatim, generates local URIs on the fly like the rest of them. * Conversation muting - prevents notifications that reference a conversation (including replies, favourites, reblogs) from being created. API endpoints /api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute Currently no way to tell when a status/conversation is muted, so the web UI only has a "disable notifications" button, doesn't work as a toggle * Display "Dismiss notifications" on all statuses in notifications column, not just own * Add "muted" as a boolean attribute on statuses JSON For now always false on contained reblogs, since it's only relevant for statuses returned from the notifications endpoint, which are not nested Remove "Disable notifications" from detailed status view, since it's only relevant in the notifications column * Up max class length * Remove pending test for conversation mute * Add tests, clean up * Rename to "mute conversation" and "unmute conversation" * Raise validation error when trying to mute/unmute status without conversation * Adding account domain blocks that filter notifications and public timelines * Add tests for domain blocks in notifications, public timelines Filter reblogs of blocked domains from home * Add API for listing and creating account domain blocks * API for creating/deleting domain blocks, tests for Status#ancestors and Status#descendants, filter domain blocks from them * Filter domains in streaming API * Update account_domain_block_spec.rb
7 years ago
Account domain blocks (#2381) * Add <ostatus:conversation /> tag to Atom input/output Only uses ref attribute (not href) because href would be the alternate link that's always included also. Creates new conversation for every non-reply status. Carries over conversation for every reply. Keeps remote URIs verbatim, generates local URIs on the fly like the rest of them. * Conversation muting - prevents notifications that reference a conversation (including replies, favourites, reblogs) from being created. API endpoints /api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute Currently no way to tell when a status/conversation is muted, so the web UI only has a "disable notifications" button, doesn't work as a toggle * Display "Dismiss notifications" on all statuses in notifications column, not just own * Add "muted" as a boolean attribute on statuses JSON For now always false on contained reblogs, since it's only relevant for statuses returned from the notifications endpoint, which are not nested Remove "Disable notifications" from detailed status view, since it's only relevant in the notifications column * Up max class length * Remove pending test for conversation mute * Add tests, clean up * Rename to "mute conversation" and "unmute conversation" * Raise validation error when trying to mute/unmute status without conversation * Adding account domain blocks that filter notifications and public timelines * Add tests for domain blocks in notifications, public timelines Filter reblogs of blocked domains from home * Add API for listing and creating account domain blocks * API for creating/deleting domain blocks, tests for Status#ancestors and Status#descendants, filter domain blocks from them * Filter domains in streaming API * Update account_domain_block_spec.rb
7 years ago
Non-Serial ("Snowflake") IDs (#4801) * Use non-serial IDs This change makes a number of nontrivial tweaks to the data model in Mastodon: * All IDs are now 8 byte integers (rather than mixed 4- and 8-byte) * IDs are now assigned as: * Top 6 bytes: millisecond-resolution time from epoch * Bottom 2 bytes: serial (within the millisecond) sequence number * See /lib/tasks/db.rake's `define_timestamp_id` for details, but note that the purpose of these changes is to make it difficult to determine the number of objects in a table from the ID of any object. * The Redis sorted set used for the feed will have values used to look up toots, rather than scores. This is almost always the same as the existing behavior, except in the case of boosted toots. This change was made because Redis stores scores as double-precision floats, which cannot store the new ID format exactly. Note that this doesn't cause problems with sorting/pagination, because ZREVRANGEBYSCORE sorts lexicographically when scores are tied. (This will still cause sorting issues when the ID gains a new significant digit, but that's extraordinarily uncommon.) Note a couple of tradeoffs have been made in this commit: * lib/tasks/db.rake is used to enforce many/most column constraints, because this commit seems likely to take a while to bring upstream. Enforcing a post-migrate hook is an easier way to maintain the code in the interim. * Boosted toots will appear in the timeline as many times as they have been boosted. This is a tradeoff due to the way the feed is saved in Redis at the moment, but will be handled by a future commit. This would effectively close Mastodon's #1059, as it is a snowflake-like system of generating IDs. However, given how involved the changes were simply within Mastodon, it may have unexpected interactions with some clients, if they store IDs as doubles (or as 4-byte integers). This was a problem that Twitter ran into with their "snowflake" transition, particularly in JavaScript clients that treated IDs as JS integers, rather than strings. It therefore would be useful to test these changes at least in the web interface and popular clients before pushing them to all users. * Fix JavaScript interface with long IDs Somewhat predictably, the JS interface handled IDs as numbers, which in JS are IEEE double-precision floats. This loses some precision when working with numbers as large as those generated by the new ID scheme, so we instead handle them here as strings. This is relatively simple, and doesn't appear to have caused any problems, but should definitely be tested more thoroughly than the built-in tests. Several days of use appear to support this working properly. BREAKING CHANGE: The major(!) change here is that IDs are now returned as strings by the REST endpoints, rather than as integers. In practice, relatively few changes were required to make the existing JS UI work with this change, but it will likely hit API clients pretty hard: it's an entirely different type to consume. (The one API client I tested, Tusky, handles this with no problems, however.) Twitter ran into this issue when introducing Snowflake IDs, and decided to instead introduce an `id_str` field in JSON responses. I have opted to *not* do that, and instead force all IDs to 64-bit integers represented by strings in one go. (I believe Twitter exacerbated their problem by rolling out the changes three times: once for statuses, once for DMs, and once for user IDs, as well as by leaving an integer ID value in JSON. As they said, "If you’re using the `id` field with JSON in a Javascript-related language, there is a very high likelihood that the integers will be silently munged by Javascript interpreters. In most cases, this will result in behavior such as being unable to load or delete a specific direct message, because the ID you're sending to the API is different than the actual identifier associated with the message." [1]) However, given that this is a significant change for API users, alternatives or a transition time may be appropriate. 1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html * Restructure feed pushes/unpushes This was necessary because the previous behavior used Redis zset scores to identify statuses, but those are IEEE double-precision floats, so we can't actually use them to identify all 64-bit IDs. However, it leaves the code in a much better state for refactoring reblog handling / coalescing. Feed-management code has been consolidated in FeedManager, including: * BatchedRemoveStatusService no longer directly manipulates feed zsets * RemoveStatusService no longer directly manipulates feed zsets * PrecomputeFeedService has moved its logic to FeedManager#populate_feed (PrecomputeFeedService largely made lots of calls to FeedManager, but didn't follow the normal adding-to-feed process.) This has the effect of unifying all of the feed push/unpush logic in FeedManager, making it much more tractable to update it in the future. Due to some additional checks that must be made during, for example, batch status removals, some Redis pipelining has been removed. It does not appear that this should cause significantly increased load, but if necessary, some optimizations are possible in batch cases. These were omitted in the pursuit of simplicity, but a batch_push and batch_unpush would be possible in the future. Tests were added to verify that pushes happen under expected conditions, and to verify reblog behavior (both on pushing and unpushing). In the case of unpushing, this includes testing behavior that currently leads to confusion such as Mastodon's #2817, but this codifies that the behavior is currently expected. * Rubocop fixes I could swear I made these changes already, but I must have lost them somewhere along the line. * Address review comments This addresses the first two comments from review of this feature: https://github.com/tootsuite/mastodon/pull/4801#discussion_r139336735 https://github.com/tootsuite/mastodon/pull/4801#discussion_r139336931 This adds an optional argument to FeedManager#key, the subtype of feed key to generate. It also tests to ensure that FeedManager's settings are such that reblogs won't be tracked forever. * Hardcode IdToBigints migration columns This addresses a comment during review: https://github.com/tootsuite/mastodon/pull/4801#discussion_r139337452 This means we'll need to make sure that all _id columns going forward are bigints, but that should happen automatically in most cases. * Additional fixes for stringified IDs in JSON These should be the last two. These were identified using eslint to try to identify any plain casts to JavaScript numbers. (Some such casts are legitimate, but these were not.) Adding the following to .eslintrc.yml will identify casts to numbers: ~~~ no-restricted-syntax: - warn - selector: UnaryExpression[operator='+'] > :not(Literal) message: Avoid the use of unary + - selector: CallExpression[callee.name='Number'] message: Casting with Number() may coerce string IDs to numbers ~~~ The remaining three casts appear legitimate: two casts to array indices, one in a server to turn an environment variable into a number. * Only implement timestamp IDs for Status IDs Per discussion in #4801, this is only being merged in for Status IDs at this point. We do this in a migration, as there is no longer use for a post-migration hook. We keep the initialization of the timestamp_id function as a Rake task, as it is also needed after db:schema:load (as db/schema.rb doesn't store Postgres functions). * Change internal streaming payloads to stringified IDs as well This is equivalent to 591a9af356faf2d5c7e66e3ec715502796c875cd from #5019, with an extra change for the addition to FeedManager#unpush. * Ensure we have a status_id_seq sequence Apparently this is not a given when specifying a custom ID function, so now we ensure it gets created. This uses the generic version of this function to more easily support adding additional tables with timestamp IDs in the future, although it would be possible to cut this down to a less generic version if necessary. It is only run during db:schema:load or the relevant migration, so the overhead is extraordinarily minimal. * Transition reblogs to new Redis format This provides a one-way migration to transition old Redis reblog entries into the new format, with a separate tracking entry for reblogs. It is not invertible because doing so could (if timestamp IDs are used) require a database query for each status in each users' feed, which is likely to be a significant toll on major instances. * Address review comments from @akihikodaki No functional changes. * Additional review changes * Heredoc cleanup * Run db:schema:load hooks for test in development This matches the behavior in Rails' ActiveRecord::Tasks::DatabaseTasks.each_current_configuration, which would otherwise break `rake db:setup` in development. It also moves some functionality out to a library, which will be a good place to put additional related functionality in the near future.
6 years ago
  1. require 'rails_helper'
  2. RSpec.describe FeedManager do
  3. it 'tracks at least as many statuses as reblogs' do
  4. expect(FeedManager::REBLOG_FALLOFF).to be <= FeedManager::MAX_ITEMS
  5. end
  6. describe '#key' do
  7. subject { FeedManager.instance.key(:home, 1) }
  8. it 'returns a string' do
  9. expect(subject).to be_a String
  10. end
  11. end
  12. describe '#filter?' do
  13. let(:alice) { Fabricate(:account, username: 'alice') }
  14. let(:bob) { Fabricate(:account, username: 'bob', domain: 'example.com') }
  15. let(:jeff) { Fabricate(:account, username: 'jeff') }
  16. context 'for home feed' do
  17. it 'returns false for followee\'s status' do
  18. status = Fabricate(:status, text: 'Hello world', account: alice)
  19. bob.follow!(alice)
  20. expect(FeedManager.instance.filter?(:home, status, bob.id)).to be false
  21. end
  22. it 'returns false for reblog by followee' do
  23. status = Fabricate(:status, text: 'Hello world', account: jeff)
  24. reblog = Fabricate(:status, reblog: status, account: alice)
  25. bob.follow!(alice)
  26. expect(FeedManager.instance.filter?(:home, reblog, bob.id)).to be false
  27. end
  28. it 'returns true for reblog by followee of blocked account' do
  29. status = Fabricate(:status, text: 'Hello world', account: jeff)
  30. reblog = Fabricate(:status, reblog: status, account: alice)
  31. bob.follow!(alice)
  32. bob.block!(jeff)
  33. expect(FeedManager.instance.filter?(:home, reblog, bob.id)).to be true
  34. end
  35. it 'returns true for reblog by followee of muted account' do
  36. status = Fabricate(:status, text: 'Hello world', account: jeff)
  37. reblog = Fabricate(:status, reblog: status, account: alice)
  38. bob.follow!(alice)
  39. bob.mute!(jeff)
  40. expect(FeedManager.instance.filter?(:home, reblog, bob.id)).to be true
  41. end
  42. it 'returns true for reblog by followee of someone who is blocking recipient' do
  43. status = Fabricate(:status, text: 'Hello world', account: jeff)
  44. reblog = Fabricate(:status, reblog: status, account: alice)
  45. bob.follow!(alice)
  46. jeff.block!(bob)
  47. expect(FeedManager.instance.filter?(:home, reblog, bob.id)).to be true
  48. end
  49. it 'returns false for reply by followee to another followee' do
  50. status = Fabricate(:status, text: 'Hello world', account: jeff)
  51. reply = Fabricate(:status, text: 'Nay', thread: status, account: alice)
  52. bob.follow!(alice)
  53. bob.follow!(jeff)
  54. expect(FeedManager.instance.filter?(:home, reply, bob.id)).to be false
  55. end
  56. it 'returns false for reply by followee to recipient' do
  57. status = Fabricate(:status, text: 'Hello world', account: bob)
  58. reply = Fabricate(:status, text: 'Nay', thread: status, account: alice)
  59. bob.follow!(alice)
  60. expect(FeedManager.instance.filter?(:home, reply, bob.id)).to be false
  61. end
  62. it 'returns false for reply by followee to self' do
  63. status = Fabricate(:status, text: 'Hello world', account: alice)
  64. reply = Fabricate(:status, text: 'Nay', thread: status, account: alice)
  65. bob.follow!(alice)
  66. expect(FeedManager.instance.filter?(:home, reply, bob.id)).to be false
  67. end
  68. it 'returns true for reply by followee to non-followed account' do
  69. status = Fabricate(:status, text: 'Hello world', account: jeff)
  70. reply = Fabricate(:status, text: 'Nay', thread: status, account: alice)
  71. bob.follow!(alice)
  72. expect(FeedManager.instance.filter?(:home, reply, bob.id)).to be true
  73. end
  74. it 'returns true for the second reply by followee to a non-federated status' do
  75. reply = Fabricate(:status, text: 'Reply 1', reply: true, account: alice)
  76. second_reply = Fabricate(:status, text: 'Reply 2', thread: reply, account: alice)
  77. bob.follow!(alice)
  78. expect(FeedManager.instance.filter?(:home, second_reply, bob.id)).to be true
  79. end
  80. it 'returns false for status by followee mentioning another account' do
  81. bob.follow!(alice)
  82. status = PostStatusService.new.call(alice, 'Hey @jeff')
  83. expect(FeedManager.instance.filter?(:home, status, bob.id)).to be false
  84. end
  85. it 'returns true for status by followee mentioning blocked account' do
  86. bob.block!(jeff)
  87. bob.follow!(alice)
  88. status = PostStatusService.new.call(alice, 'Hey @jeff')
  89. expect(FeedManager.instance.filter?(:home, status, bob.id)).to be true
  90. end
  91. it 'returns true for reblog of a personally blocked domain' do
  92. alice.block_domain!('example.com')
  93. alice.follow!(jeff)
  94. status = Fabricate(:status, text: 'Hello world', account: bob)
  95. reblog = Fabricate(:status, reblog: status, account: jeff)
  96. expect(FeedManager.instance.filter?(:home, reblog, alice.id)).to be true
  97. end
  98. end
  99. context 'for mentions feed' do
  100. it 'returns true for status that mentions blocked account' do
  101. bob.block!(jeff)
  102. status = PostStatusService.new.call(alice, 'Hey @jeff')
  103. expect(FeedManager.instance.filter?(:mentions, status, bob.id)).to be true
  104. end
  105. it 'returns true for status that replies to a blocked account' do
  106. status = Fabricate(:status, text: 'Hello world', account: jeff)
  107. reply = Fabricate(:status, text: 'Nay', thread: status, account: alice)
  108. bob.block!(jeff)
  109. expect(FeedManager.instance.filter?(:mentions, reply, bob.id)).to be true
  110. end
  111. it 'returns true for status by silenced account who recipient is not following' do
  112. status = Fabricate(:status, text: 'Hello world', account: alice)
  113. alice.update(silenced: true)
  114. expect(FeedManager.instance.filter?(:mentions, status, bob.id)).to be true
  115. end
  116. it 'returns false for status by followed silenced account' do
  117. status = Fabricate(:status, text: 'Hello world', account: alice)
  118. alice.update(silenced: true)
  119. bob.follow!(alice)
  120. expect(FeedManager.instance.filter?(:mentions, status, bob.id)).to be false
  121. end
  122. end
  123. end
  124. describe '#push' do
  125. it 'trims timelines if they will have more than FeedManager::MAX_ITEMS' do
  126. account = Fabricate(:account)
  127. status = Fabricate(:status)
  128. members = FeedManager::MAX_ITEMS.times.map { |count| [count, count] }
  129. Redis.current.zadd("feed:type:#{account.id}", members)
  130. FeedManager.instance.push('type', account, status)
  131. expect(Redis.current.zcard("feed:type:#{account.id}")).to eq FeedManager::MAX_ITEMS
  132. end
  133. it 'sends push updates for non-home timelines' do
  134. account = Fabricate(:account)
  135. status = Fabricate(:status)
  136. allow(Redis.current).to receive_messages(publish: nil)
  137. FeedManager.instance.push('type', account, status)
  138. expect(Redis.current).to have_received(:publish).with("timeline:#{account.id}", any_args).at_least(:once)
  139. end
  140. context 'reblogs' do
  141. it 'saves reblogs of unseen statuses' do
  142. account = Fabricate(:account)
  143. reblogged = Fabricate(:status)
  144. reblog = Fabricate(:status, reblog: reblogged)
  145. expect(FeedManager.instance.push('type', account, reblog)).to be true
  146. end
  147. it 'does not save a new reblog of a recent status' do
  148. account = Fabricate(:account)
  149. reblogged = Fabricate(:status)
  150. reblog = Fabricate(:status, reblog: reblogged)
  151. FeedManager.instance.push('type', account, reblogged)
  152. expect(FeedManager.instance.push('type', account, reblog)).to be false
  153. end
  154. it 'saves a new reblog of an old status' do
  155. account = Fabricate(:account)
  156. reblogged = Fabricate(:status)
  157. reblog = Fabricate(:status, reblog: reblogged)
  158. FeedManager.instance.push('type', account, reblogged)
  159. # Fill the feed with intervening statuses
  160. FeedManager::REBLOG_FALLOFF.times do
  161. FeedManager.instance.push('type', account, Fabricate(:status))
  162. end
  163. expect(FeedManager.instance.push('type', account, reblog)).to be true
  164. end
  165. it 'does not save a new reblog of a recently-reblogged status' do
  166. account = Fabricate(:account)
  167. reblogged = Fabricate(:status)
  168. reblogs = 2.times.map { Fabricate(:status, reblog: reblogged) }
  169. # The first reblog will be accepted
  170. FeedManager.instance.push('type', account, reblogs.first)
  171. # The second reblog should be ignored
  172. expect(FeedManager.instance.push('type', account, reblogs.last)).to be false
  173. end
  174. it 'saves a new reblog of a long-ago-reblogged status' do
  175. account = Fabricate(:account)
  176. reblogged = Fabricate(:status)
  177. reblogs = 2.times.map { Fabricate(:status, reblog: reblogged) }
  178. # The first reblog will be accepted
  179. FeedManager.instance.push('type', account, reblogs.first)
  180. # Fill the feed with intervening statuses
  181. FeedManager::REBLOG_FALLOFF.times do
  182. FeedManager.instance.push('type', account, Fabricate(:status))
  183. end
  184. # The second reblog should also be accepted
  185. expect(FeedManager.instance.push('type', account, reblogs.last)).to be true
  186. end
  187. end
  188. end
  189. describe '#unpush' do
  190. it 'leaves a reblogged status when deleting the reblog' do
  191. account = Fabricate(:account)
  192. reblogged = Fabricate(:status)
  193. status = Fabricate(:status, reblog: reblogged)
  194. FeedManager.instance.push('type', account, status)
  195. # The reblogging status should show up under normal conditions.
  196. expect(Redis.current.zrange("feed:type:#{account.id}", 0, -1)).to eq [status.id.to_s]
  197. FeedManager.instance.unpush('type', account, status)
  198. # Because we couldn't tell if the status showed up any other way,
  199. # we had to stick the reblogged status in by itself.
  200. expect(Redis.current.zrange("feed:type:#{account.id}", 0, -1)).to eq [reblogged.id.to_s]
  201. end
  202. it 'sends push updates' do
  203. account = Fabricate(:account)
  204. status = Fabricate(:status)
  205. FeedManager.instance.push('type', account, status)
  206. allow(Redis.current).to receive_messages(publish: nil)
  207. FeedManager.instance.unpush('type', account, status)
  208. deletion = Oj.dump(event: :delete, payload: status.id.to_s)
  209. expect(Redis.current).to have_received(:publish).with("timeline:#{account.id}", deletion)
  210. end
  211. end
  212. end