Rounding errors
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
Research direction
The issue names no file, so begin by finding where the Kotlin source evaluates division followed by multiplication, and reproduce the two steps (100÷3, then ×3) on the app. Confirm whether the fix belongs in the arithmetic itself or in how the result is rounded for display, since the maintainers have not said which. Done means the sequence shows 100 and the change is covered by a test.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.4.0
Affected Android/Custom ROM version
GrapheneOS 2026062801 (Android 17)
Affected device model
Pixel 8
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Type
100÷3and press equals - Type
×3and press equals
Expected behavior
The calculation should return 100.
Actual behavior
The calculation returns 99.999999999999999
Screenshots/Screen recordings
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 450
- Forks
- 57
- Avg merge
- 7d 35m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Calculator
-
feature request needs triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
FossifyOrg/Calculator#320 ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
FossifyOrg/Calculator#338 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Calculator#325 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FossifyOrg/Calculator#313 · 1 reaction ·
Maintainers usually reply within 5 days
-
Percentual (%) operations not saved in historyPossibly taken @Guflly claimed this 70 days ago. Openbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
FossifyOrg/Calculator#304 · 1 comment ·
Maintainers usually reply within 5 days
All issues in FossifyOrg/Calculator
Similar issues
-
bugbane/qf good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
osservatorionessuno/bugbane#173 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Bayern feature:Application ready web
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
digitalfabrik/entitlementcard#3176 ·
Maintainers usually reply within 7 days
-
bug need-device
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
ramesh130/superplayer#495 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
maxrave-dev/SimpMusic#2649 ·
Maintainers usually reply within 2 days