You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently 315 warnings WITH a null account_id, and 322 without, so it appears to have been happening for a while, but stopped in feb.
mastodon=> select max(created_at), min(created_at) from account_warnings where account_id is null;
max | min
----------------------------+----------------------------
2023-02-16 06:12:50.031092 | 2022-11-16 09:56:26.437818
(1 row)
mastodon=>
Expected behaviour
Not have crashed
Actual behaviour
Crashed
Detailed description
I suspect this was brought upon by running an expire in (I assume) Feburary.
As the constraint explicitly says to null the account_id col, the view should be able to handle account_warning.account being null without crashing.
My workaround for the moment will just be to set the account_id to be target_account_id, but that won't fix it for someone else who runs an expire and then has no idea why they can't see the admin page of random accounts.
Specifications
v4.1.4
The text was updated successfully, but these errors were encountered:
Steps to reproduce the problem
When trying to view the admin page of the account below, an error is generated:
https://github.com/mastodon/mastodon/blob/main/app/views/admin/account_warnings/_account_warning.html.haml#L8
Querying the account_warnings table, the reporter ID has been nulled:
It appears that the foreign key here nullifies the account_id when the reporting account is deleted
https://github.com/mastodon/mastodon/blob/main/db/schema.rb#L1163
There are currently 315 warnings WITH a null account_id, and 322 without, so it appears to have been happening for a while, but stopped in feb.
Expected behaviour
Not have crashed
Actual behaviour
Crashed
Detailed description
I suspect this was brought upon by running an expire in (I assume) Feburary.
As the constraint explicitly says to null the account_id col, the view should be able to handle account_warning.account being null without crashing.
My workaround for the moment will just be to set the account_id to be target_account_id, but that won't fix it for someone else who runs an expire and then has no idea why they can't see the admin page of random accounts.
Specifications
v4.1.4
The text was updated successfully, but these errors were encountered: