Issue with --top-directory

[sepro]

I found two potential issues with the --top-directory parameter

The command below picks up the folder ont (as intended) but also the folder ontnext in the same staging folder.

duduckdb /data/leuven/public/staging-stats/stg_00063.parquet --human-readable --top-directory=ont/

...
ont/benchmark:           7.2GiB           1.5Ki           
ont/databases:           1.4TiB           245.9Ki         
ontnext/scripts:         38.8KiB          6.0             
ontnext/snakemake:       940.3MiB         50.3Ki
...

Attempting to use a lower level folder as the top returns empty results.

duduckdb /data/leuven/public/staging-stats/stg_00063.parquet --human-readable --top-directory=ont/databases

WARNING:root:The data was collected on 2025-04-28 04:31:21.704938308 +0200 CEST 
WARNING:root:The reported usage is a snapshot of the usage around that time
directory:               size             inodes          
================================================================================

[stevenvdb]

The command below picks up the folder ont (as intended) but also the folder ontnext in the same staging folder.

This is indeed a bug, it should be fixed by #3

Attempting to use a lower level folder as the top returns empty results.

This is the expected behavior. The depth is always counted from the root, so if you specify --top-directory=ont/databases, you need to set --max-depth to at least 2 (the default is 1). We could of course also change the behavior and count the depth from the top directory, but that would also be confusing.

[sepro]

Thanks ! I'll test out the solution after the weekend !

(To me actually starting to count the depth from the specified top directory actually is less confusing)