bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #321] Is it possible to set the unit of measurement to a specified value,like KB? #141

New Issue
Closed
opened 2026-06-08 11:25:51 +03:00 by zhus · 13 comments
zhus commented 2026-06-08 11:25:51 +03:00
Owner
Copy Link
Copy Source

Originally created by @TYzzt on GitHub (Apr 3, 2023).
Original GitHub issue: https://github.com/bootandy/dust/issues/321

When the size of storage is large, the accuracy loses the angle

Originally created by @TYzzt on GitHub (Apr 3, 2023). Original GitHub issue: https://github.com/bootandy/dust/issues/321 When the size of storage is large, the accuracy loses the angle
zhus closed this issue 2026-06-08 11:25:51 +03:00
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@TYzzt commented on GitHub (Apr 10, 2023):

https://github.com/bootandy/dust/pull/322

<!-- gh-comment-id:1501512310 --> @TYzzt commented on GitHub (Apr 10, 2023): [https://github.com/bootandy/dust/pull/322](url)
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (May 5, 2023):

I'm not particularly keen on adding this flag. What is the usecase for it?

If you need to know the exact size of a file you can use du for that.

dust is going to ignore several files anyway with its targetted summary so I'm not sure what value this adds.

<!-- gh-comment-id:1536669463 --> @bootandy commented on GitHub (May 5, 2023): I'm not particularly keen on adding this flag. What is the usecase for it? If you need to know the exact size of a file you can use du for that. dust is going to ignore several files anyway with its targetted summary so I'm not sure what value this adds.
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@TYzzt commented on GitHub (May 6, 2023):

Fast and relatively accurate estimation of storage usage in HPC distributed storage scenarios

<!-- gh-comment-id:1537111263 --> @TYzzt commented on GitHub (May 6, 2023): > Fast and relatively accurate estimation of storage usage in HPC distributed storage scenarios
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (May 7, 2023):

Hmm, maybe, let me sleep on it.

<!-- gh-comment-id:1537370236 --> @bootandy commented on GitHub (May 7, 2023): Hmm, maybe, let me sleep on it.
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@sergeevabc commented on GitHub (Feb 18, 2024):

How do I get the size in bytes? When I share files, I prefer to specify the size in bytes so that people don't get confused (KB, KiB, etc). In addition, one can later process the output in bytes by other programs, such as awk, and convert it to the desired units.

<!-- gh-comment-id:1951419916 --> @sergeevabc commented on GitHub (Feb 18, 2024): How do I get the size in bytes? When I share files, I prefer to specify the size in bytes so that people don't get confused (KB, KiB, etc). In addition, one can later process the output in bytes by other programs, such as awk, and convert it to the desired units.
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@cgkantidis commented on GitHub (Feb 19, 2024):

Please add a --format option, to specify the output's size format.

I want to parse the output from another script (in Python in my case) to merge it with other reports.
I prefer to call dust in a subprocess, and parse its output, because it's much faster than a native-Python solution.
But I don't want to turn my Python script which merges reports to Rust, because it would be too much work and it's already fast enough.

Any chance to implement that?

dua offers this option:

  -f, --format <FORMAT>
          The format with which to print byte counts

          [default: binary]
          [possible values: metric, binary, bytes, gb, gib, mb, mib]
<!-- gh-comment-id:1952414162 --> @cgkantidis commented on GitHub (Feb 19, 2024): Please add a `--format` option, to specify the output's size format. I want to parse the output from another script (in Python in my case) to merge it with other reports. I prefer to call `dust` in a subprocess, and parse its output, because it's much faster than a native-Python solution. But I don't want to turn my Python script which merges reports to Rust, because it would be too much work and it's already fast enough. Any chance to implement that? `dua` offers this option: ``` -f, --format <FORMAT> The format with which to print byte counts [default: binary] [possible values: metric, binary, bytes, gb, gib, mb, mib] ```
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Feb 19, 2024):

Ok, clearly people want this. I'll look into it.

<!-- gh-comment-id:1953117078 --> @bootandy commented on GitHub (Feb 19, 2024): Ok, clearly people want this. I'll look into it.
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Feb 22, 2024):

We could merge the --format flag with the --iso flag. - they seem to do similar things.

<!-- gh-comment-id:1958083168 --> @bootandy commented on GitHub (Feb 22, 2024): We could merge the --format flag with the --iso flag. - they seem to do similar things.
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@nda-cunh commented on GitHub (Mar 14, 2024):

I also need this feature. currently i'm forced to use du which is extremely slow and slows down an important script. i wanted to replace it with dust but it forces the -h (human readable). a --format or the inverse of a -h even if it's not precise would be great! thank !

<!-- gh-comment-id:1996186967 --> @nda-cunh commented on GitHub (Mar 14, 2024): I also need this feature. currently i'm forced to use du which is extremely slow and slows down an important script. i wanted to replace it with dust but it forces the -h (human readable). a --format or the inverse of a -h even if it's not precise would be great! thank !
zhus commented 2026-06-08 11:25:51 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Mar 15, 2024):

https://github.com/bootandy/dust/pull/373

it's merged it'll be in the next release.

<!-- gh-comment-id:1998498720 --> @bootandy commented on GitHub (Mar 15, 2024): https://github.com/bootandy/dust/pull/373 it's merged it'll be in the next release.
zhus commented 2026-06-08 11:25:52 +03:00
Author
Owner
Copy Link
Copy Source

@sergeevabc commented on GitHub (Apr 16, 2024):

@bootandy, every time I run dust.exe on Windows 7 x64 the first thing that appears on the screen is the following line: “This version of Windows does not support ANSI colors”. Not sure why it happens, since, for example, ripgrep and bat render colors fine. Anyway, I don't want to feel second-rate here.

<!-- gh-comment-id:2058103220 --> @sergeevabc commented on GitHub (Apr 16, 2024): @bootandy, every time I run dust.exe on Windows 7 x64 the first thing that appears on the screen is the following line: “This version of Windows does not support ANSI colors”. Not sure why it happens, since, for example, [ripgrep](https://github.com/BurntSushi/ripgrep) and [bat](https://github.com/sharkdp/bat) render colors fine. Anyway, I don't want to feel second-rate here.
zhus commented 2026-06-08 11:25:52 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Apr 17, 2024):

I don't have a windows box. - Does dust go on to print with colors or not ?

Does this happen with all versions ?

<!-- gh-comment-id:2060556196 --> @bootandy commented on GitHub (Apr 17, 2024): I don't have a windows box. - Does dust go on to print with colors or not ? Does this happen with all versions ?
zhus commented 2026-06-08 11:25:52 +03:00
Author
Owner
Copy Link
Copy Source

@sergeevabc commented on GitHub (May 13, 2024):

$ dust.v.0.5.0.exe C:\TEMP
thread 'main' panicked at 'Couldn't enable color support: 87', src\libcore\result.rs:1188:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

$ dust.v.1.0.0.exe C:\TEMP
This version of Windows does not support ANSI colors
1.2M     ┌── 25ac4429-4010-4cb0-ae65-ff1163082860.tmp                │█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │   1%

1.7M     ├── c3846ae4-d804-49ac-9640-961b052d976a.tmp                │█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │   2%

2.3M     ├── 8970d8850fb3c3cfc8eb4b517bc2fd39f84670c1.megatools.cache│██░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │   2
...
<!-- gh-comment-id:2107629503 --> @sergeevabc commented on GitHub (May 13, 2024): ``` console $ dust.v.0.5.0.exe C:\TEMP thread 'main' panicked at 'Couldn't enable color support: 87', src\libcore\result.rs:1188:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace. $ dust.v.1.0.0.exe C:\TEMP This version of Windows does not support ANSI colors 1.2M ┌── 25ac4429-4010-4cb0-ae65-ff1163082860.tmp │█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │ 1% 1.7M ├── c3846ae4-d804-49ac-9640-961b052d976a.tmp │█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │ 2% 2.3M ├── 8970d8850fb3c3cfc8eb4b517bc2fd39f84670c1.megatools.cache│██░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │ 2 ... ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#141
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?