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.

149 lines
4.5 KiB

Change IDs to strings rather than numbers in API JSON output (#5019) * 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 * 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. * Back out RelationshipsController Change This was made to make a test a bit less flakey, but has nothing to do with this branch. * Change internal streaming payloads to stringified IDs as well Per https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452 we need these changes to send deleted status IDs as strings, not integers.
6 years ago
  1. # frozen_string_literal: true
  2. class RemoveStatusService < BaseService
  3. include Redisable
  4. include Payloadable
  5. def call(status, **options)
  6. @payload = Oj.dump(event: :delete, payload: status.id.to_s)
  7. @status = status
  8. @account = status.account
  9. @tags = status.tags.pluck(:name).to_a
  10. @mentions = status.active_mentions.includes(:account).to_a
  11. @reblogs = status.reblogs.includes(:account).to_a
  12. @stream_entry = status.stream_entry
  13. @options = options
  14. RedisLock.acquire(lock_options) do |lock|
  15. if lock.acquired?
  16. remove_from_self if status.account.local?
  17. remove_from_followers
  18. remove_from_lists
  19. remove_from_affected
  20. remove_reblogs
  21. remove_from_hashtags
  22. remove_from_public
  23. remove_from_media if status.media_attachments.any?
  24. @status.destroy!
  25. else
  26. raise Mastodon::RaceConditionError
  27. end
  28. end
  29. # There is no reason to send out Undo activities when the
  30. # cause is that the original object has been removed, since
  31. # original object being removed implicitly removes reblogs
  32. # of it. The Delete activity of the original is forwarded
  33. # separately.
  34. return if !@account.local? || @options[:original_removed]
  35. remove_from_remote_followers
  36. remove_from_remote_affected
  37. end
  38. private
  39. def remove_from_self
  40. FeedManager.instance.unpush_from_home(@account, @status)
  41. end
  42. def remove_from_followers
  43. @account.followers_for_local_distribution.reorder(nil).find_each do |follower|
  44. FeedManager.instance.unpush_from_home(follower, @status)
  45. end
  46. end
  47. def remove_from_lists
  48. @account.lists_for_local_distribution.select(:id, :account_id).reorder(nil).find_each do |list|
  49. FeedManager.instance.unpush_from_list(list, @status)
  50. end
  51. end
  52. def remove_from_affected
  53. @mentions.map(&:account).select(&:local?).each do |account|
  54. redis.publish("timeline:#{account.id}", @payload)
  55. end
  56. end
  57. def remove_from_remote_affected
  58. # People who got mentioned in the status, or who
  59. # reblogged it from someone else might not follow
  60. # the author and wouldn't normally receive the
  61. # delete notification - so here, we explicitly
  62. # send it to them
  63. target_accounts = (@mentions.map(&:account).reject(&:local?) + @reblogs.map(&:account).reject(&:local?))
  64. target_accounts << @status.reblog.account if @status.reblog? && !@status.reblog.account.local?
  65. target_accounts.uniq!(&:id)
  66. # ActivityPub
  67. ActivityPub::DeliveryWorker.push_bulk(target_accounts.select(&:activitypub?).uniq(&:preferred_inbox_url)) do |target_account|
  68. [signed_activity_json, @account.id, target_account.preferred_inbox_url]
  69. end
  70. end
  71. def remove_from_remote_followers
  72. # ActivityPub
  73. ActivityPub::DeliveryWorker.push_bulk(@account.followers.inboxes) do |inbox_url|
  74. [signed_activity_json, @account.id, inbox_url]
  75. end
  76. relay! if relayable?
  77. end
  78. def relayable?
  79. @status.public_visibility?
  80. end
  81. def relay!
  82. ActivityPub::DeliveryWorker.push_bulk(Relay.enabled.pluck(:inbox_url)) do |inbox_url|
  83. [signed_activity_json, @account.id, inbox_url]
  84. end
  85. end
  86. def signed_activity_json
  87. @signed_activity_json ||= Oj.dump(serialize_payload(@status, @status.reblog? ? ActivityPub::UndoAnnounceSerializer : ActivityPub::DeleteSerializer, signer: @account))
  88. end
  89. def remove_reblogs
  90. # We delete reblogs of the status before the original status,
  91. # because once original status is gone, reblogs will disappear
  92. # without us being able to do all the fancy stuff
  93. @reblogs.each do |reblog|
  94. RemoveStatusService.new.call(reblog, original_removed: true)
  95. end
  96. end
  97. def remove_from_hashtags
  98. @account.featured_tags.where(tag_id: @status.tags.pluck(:id)).each do |featured_tag|
  99. featured_tag.decrement(@status.id)
  100. end
  101. return unless @status.public_visibility?
  102. @tags.each do |hashtag|
  103. redis.publish("timeline:hashtag:#{hashtag}", @payload)
  104. redis.publish("timeline:hashtag:#{hashtag}:local", @payload) if @status.local?
  105. end
  106. end
  107. def remove_from_public
  108. return unless @status.public_visibility?
  109. redis.publish('timeline:public', @payload)
  110. redis.publish('timeline:public:local', @payload) if @status.local?
  111. end
  112. def remove_from_media
  113. return unless @status.public_visibility?
  114. redis.publish('timeline:public:media', @payload)
  115. redis.publish('timeline:public:local:media', @payload) if @status.local?
  116. end
  117. def lock_options
  118. { redis: Redis.current, key: "distribute:#{@status.id}" }
  119. end
  120. end