If any #mastoadmins want to test this out themselves, this is the query I used to find the messed up polls:

SELECT
polls.created_at
, polls.id
, polls.account_id
, polls.votes_count
, pv.total_votes
, polls.status_id
, ARRAY_LENGTH(polls.options, 1)
FROM polls
INNER JOIN users ON
users.account_id = polls.account_id
INNER JOIN (
SELECT
poll_id
, COUNT(*) AS total_votes
FROM poll_votes
GROUP BY poll_id
) AS pv ON
pv.poll_id = polls.id
WHERE pv.total_votes > polls.votes_count
ORDER BY polls.created_at ASC;

then this to find the polls that are not messed up within the same time period:

SELECT
polls.created_at
, polls.id
, polls.account_id
, polls.votes_count
, pv.total_votes
, polls.status_id
, ARRAY_LENGTH(polls.options, 1)
FROM polls
INNER JOIN users ON
users.account_id = polls.account_id
INNER JOIN (
SELECT
poll_id
, COUNT(*) AS total_votes
FROM poll_votes
GROUP BY poll_id
) AS pv ON
pv.poll_id = polls.id
WHERE
polls.created_at >= '2025-03-04 23:03:26'
AND pv.total_votes <= polls.votes_count
ORDER BY polls.created_at ASC;

The good ones all have options array length <= 4 and the bad ones all have options array length > 4

The way I increased the poll options was by modifying MAX_OPTIONS in app/validators/poll_options_validator.rb. This appeared to work prior to v4.3.4.

Edit: Adding this here for visibility. This was not a bug in the Mastodon code, but rather the result of me increasing the max poll options on the web server but not on the server running the sidekiq processes.

More details here: https://github.com/mastodon/mastodon/issues/34662

@theropologist from mas.to (obviously) via Moshidon, which does sometimes act differently to the web version of Masto, I see all the options.

Which is cool. Preferential and/or approval voting next @Gargron? 😉

@theropologist weird... yeah that def seems to be the case. (pics taken at same time, I picked Erato since it had no votes, it says 16 votes for your instance and no vote for it, and on mine it says 15 votes yet I voted for it (selected) and still showed 0.

I've since refreshed and both show 21 votes.. and still 0% for my choice. It's like it counted the vote # but didn't record it right.

@theropologist Negative result from over here. All looks consistent here with the votes showing on Old Mermaid Town matching what I see on beige.party's web UI. The eight vote counts do add up to 42 as expected.

Edit: I now understand that the bug is that a lot more than 42 people voted; the 42 is probably just the voters on beige.party.