nextcloud / nextcloud/user_usage_report
Integer overflow in used space of user
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 45
- Forks
- 12
- Avg merge
- 13h 25m
- Merged PRs (30d)
- 19
Description
The report runs in an integer overflow for the "Disk space consumed by home storage in bytes." It maximally shows 2147483647 (2**32-1, max of int32) but works if the used storage is small than this.
Could be, that https://github.com/nextcloud/user_usage_report/issues/19#issue-338192232 wanted to point on this as well, as I am also using external storage as the primary location.
Contributor 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.
Research direction
Start by tracing how the report calculates and stores “Disk space consumed by home storage in bytes,” including the external-storage case described here; compare the behavior with issue #19. Done means the report can represent usage above 2147483647 bytes and still reports the correct value when external storage is the primary location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100