Incorrect percentages for multiple selection polls[bug] #485

New Issue

Open

opened 2023-02-25 22:41:41 +00:00 by LunaDragofelis · 3 comments

LunaDragofelis commented

2023-02-25 22:41:41 +00:00

Your setup

OTP

Extra details

No response

Version

No response

PostgreSQL version

No response

What were you trying to do?

View results of a remote multiple selection poll from AkkomaFE and from Husky, using fedi.criminallycute.fi

What did you expect to happen?

The individual options' percentages to be shown as the percentage of people who voted for that option, with the total exceeding 100% due to it being a poll where people can vote for multiple options at the same time.

This is the way it is displayed on Mastodon.

I also think that might be how it worked on Akkoma in the past, but I'm not 100% sure.

What actually happened?

Percentages are shown as the percentage of individual votes, showing numbers which are too low. Same incorrect numbers are shown on Husky and AkkomaFE, hinting at this being a backend issue.

Logs

No response

Severity

I can manage

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup OTP ### Extra details _No response_ ### Version _No response_ ### PostgreSQL version _No response_ ### What were you trying to do? View results of a remote multiple selection poll from AkkomaFE and from Husky, using fedi.criminallycute.fi ### What did you expect to happen? The individual options' percentages to be shown as the percentage of people who voted for that option, with the total exceeding 100% due to it being a poll where people can vote for multiple options at the same time. This is the way it is displayed on Mastodon. I also think that might be how it worked on Akkoma in the past, but I'm not 100% sure. ### What actually happened? Percentages are shown as the percentage of individual votes, showing numbers which are too low. Same incorrect numbers are shown on Husky and AkkomaFE, hinting at this being a backend issue. ### Logs _No response_ ### Severity I can manage ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

Screenshot_2023-02-25-23-20-59-727_org.mozilla.firefox.jpg

409 KiB

Screenshot_2023-02-25-23-21-10-513_org.mozilla.firefox.jpg

374 KiB

Screenshot_2023-02-25-23-20-59-727_org.mozilla.firefox.jpg

Screenshot_2023-02-25-23-21-10-513_org.mozilla.firefox.jpg

LunaDragofelis added the

bug

label 2023-02-25 22:41:41 +00:00

LunaDragofelis commented

2023-02-25 22:42:29 +00:00

Author

I'm not the instance admin, that'd be @siina@fedi.criminallycute.fi

Oneric referenced this issue

2024-04-26 00:55:59 +00:00

meta: closeable issues #758

bjo commented

2024-04-29 21:08:32 +00:00

I also got incorrect percentages with Moshidon like "120%".

Oneric commented

2024-04-30 16:00:50 +00:00

Member

I also got incorrect percentages with Moshidon like "120%".

If it just happens with Mastodon-tailored apps on multi-option polls, this is #190

iiuc #190 shouldn’t affect akkoma-fe though, but without more logs it’s basically impossible to tell if the numbers OP reported for akkoma-fe are actually due to a bug or just normal federation desync

> I also got incorrect percentages with Moshidon like "120%". If it just happens with Mastodon-tailored apps on multi-option polls, this is #190 iiuc #190 shouldn’t affect akkoma-fe though, but without more logs it’s basically impossible to tell if the numbers OP reported for akkoma-fe are actually due to a bug or just normal federation desync

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#485

No description provided.