-
-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Migrate all old direct messages to new conversations schema #9085
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
class MigrateAccountConversations < ActiveRecord::Migration[5.2] | ||
disable_ddl_transaction! | ||
|
||
def up | ||
say '' | ||
say 'WARNING: This migration may take a *long* time for large instances' | ||
say 'It will *not* lock tables for any significant time, but it may run' | ||
say 'for a very long time. We will pause for 10 seconds to allow you to' | ||
say 'interrupt this migration if you are not ready.' | ||
say '' | ||
|
||
10.downto(1) do |i| | ||
say "Continuing in #{i} second#{i == 1 ? '' : 's'}...", true | ||
sleep 1 | ||
end | ||
|
||
local_direct_statuses.find_each do |status| | ||
AccountConversation.add_status(status.account, status) | ||
end | ||
|
||
notifications_about_direct_statuses.find_each do |notification| | ||
AccountConversation.add_status(notification.account, notification.target_status) | ||
end | ||
end | ||
|
||
def down | ||
end | ||
|
||
private | ||
|
||
def local_direct_statuses | ||
Status.unscoped | ||
.local | ||
.where(visibility: :direct) | ||
.includes(:account, mentions: :account) | ||
end | ||
|
||
def notifications_about_direct_statuses | ||
Notification.joins(mention: :status) | ||
.where(activity_type: 'Mention', statuses: { visibility: :direct }) | ||
.includes(:account, mention: { status: [:account, mentions: :account] }) | ||
end | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What about deleted notifications (of statuses that would still be in the DM column)? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The alternative is not worth it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't know, we currently have a way to clear the notifications, so people might do that. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No I mean the alternative is running the NotifyService code which performs a lot of checks that are not optimized for n+1. It's a lot faster to iterate over already existing notifications. Also if you deleted the notifications it might be you don't wanna see those DMs anymore anyway. Overall I think it's the most optimal choice for the migration. |
||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about statuses being added out-of-order?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Batch query enforces own order and it's based on id and i think it's ascending.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any local toot will still be added before any remote toot, regardless of their actual order, right?
This means that if the last toot of a conversation was a local toot, it won't actually show, and that removing toots from the conversation will lead to strange behaviors.
It also means that for servers running on master or the previous RC, old toots will pop up on top of existing conversations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You forget the status_ids are sorted before being saved, so inserting out of order should be fine. Updates will be streamed though but only if you are connected to the direct stream and I think even then it's a minor one-off issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry, I can't find where they are sorted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/tootsuite/mastodon/blob/master/app/models/account_conversation.rb#L99-L102