Unix socket files seem to have negative size

Open
  • Is something wrong?
#149 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
fsharp
Domain
cli, operating-systems

Research direction

The report names no file, test, or entry point. Reproduce cleanup of the reported .sock path, trace how the tool obtains and formats file size, and add coverage for Unix socket entries; done means socket files no longer produce an incorrect negative size while cleanup still succeeds.

Written by the indexing model from the issue text.

Description

bug help wanted

From today's session:

emoving file T:\Temp\jb.station.ij.156404.sock (-1.00 B)… ok
Dominant language
F#
Stars
9
Forks
1
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.