Incorrect display of group information in larger directories

[moderation]

It looks like this is the more up to date repo vs. https://tangled.sh/@rockorager.dev/lsr

When listing files in directories that contains > 256 files with lsr --long --time I always end up with one file being shown with the incorrect user and group of root with the wrong size and date. Same result omitting --time.

-rw-r--r-- moderation moderation    5.1 KB 31 May  2008  icon.jpg
-rw-rw-r-- moderation moderation  646.9 KB 22 Oct  2007 󰈤 opera.adr
---------- root       root            0 B  31 Dec  1969  inf70.pdf

The following fixes it for me but not entirely sure on correctness:

diff --git a/src/main.zig b/src/main.zig
index a48bb02..3e522d6 100644
--- a/src/main.zig
+++ b/src/main.zig
@@ -1047,7 +1047,7 @@ fn onCompletion(io: *ourio.Ring, task: ourio.Task) anyerror!void {

             for (cmd.entries, 0..) |*entry, i| {
                 if (i >= queue_size) {
-                    cmd.entry_idx = i;
+                    cmd.entry_idx = i - 1;
                     break;
                 }
                 const path = try std.fs.path.joinZ(

[dchinmay2]

Looks like it has to do with the queue size being 256:

lsr/src/main.zig

Line 34 in 833935b

const queue_size = 256;

If I change it to 512 all of them show the correct user and group

[moderation]

I tested reverting my change, changing the queue size and I still get the same end result. However unlike https://tangled.org/rockorager.dev/lsr/issues/11 where the 255th result is impacted, the 123rd entry is impacted with the bigger queue size

[dchinmay2]

I created a folder with 257 files, and tested mine with and without changing the queue size from 256 to 512 - how many files are there in your directory?

[moderation]

~/Library/zig/0.15.2/lsr/zig-out/bin/lsr --long --time | wc -l
1117

[dchinmay2]

I think you should try 2048 then

…

On Fri, Dec 12, 2025, 16:02 moderation ***@***.***> wrote: *moderation* left a comment (rockorager/lsr#5) <#5 (comment)> ~/Library/zig/0.15.2/lsr/zig-out/bin/lsr --long --time | wc -l 1117 — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIWNSZ5DDGFXMKH7NYRJQC34BMUNBAVCNFSM6AAAAACFFTIGDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBYGEZTANBRGU> . You are receiving this because you commented.Message ID: ***@***.***>

[moderation]

A flexible approach where prior knowledge of directory size, and and hard coding the queue size to be larger, would be ideal

[dchinmay2]

No I meant, can you try 2048? If it works for 2048 (but not any power of 2 below 1117) then we can narrow it down to this being the cause

Edit: nevermind, I tried it myself and can confirm this

[dchinmay2]

it's also interesting that uid and gid are 0 (it says root) but mtime is -1 (31 dec 1969) (which is a bit pattern of all ones)

[moderation]

I just tried 2048 and it works. Do we think that is the correct fix?

[dchinmay2]

I don't think so, this is just a band-aid. u16 maxes out at 65535 while the number of children in a directory can be much more than that - so even if you do set it to the max value of the type the bug has to be fixed properly