Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

A case of incorrectly reported size

Open
#83 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
fsharp
Domain
cli

Research direction

Start by reproducing the reported negative size and tracing how Vacuum obtains and formats file sizes; the issue names no source file or test. Check handling of files larger than 2 or 4 GiB, and consider the work done when reported sizes remain correct and non-negative for those files.

Written by the indexing model from the issue text.

Description

bug

I had a case when Vacuum reported a file size of -1841943067.00 B which is definitely incorrect.

Need to investigate how this is possible. Maybe we determine certain file sizes incorrectly, like files of more than 2 or 4 GiB.

Dominant language
F#
Stars
9
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ForNeVeR/Vacuum

All issues in ForNeVeR/Vacuum

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.