krino.git/internal/extract, branch mainrule-based file sorter in Go, shows the plan before touching anything, applies only the files you choose, and can undo any run, with s-expression rules and a GTK 4 windowhttps://git.labunix.xyz/krino.git/atom?h=main2026-09-17T12:07:37Zmax-read bounds what a file becomes, not only what is read2026-09-17T12:07:37ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:07:37Zurn:sha1:4c6fadfab5434317357ad0272ace7927d2945942
max-read gates on file size before reading, then the text was read
whole and decoded: a file that is not valid UTF-8 decodes one byte per
code point and doubles, and normalising and folding copy that again per
set of options, with GOMAXPROCS files in flight. Twelve 40 MB files
reached 3.3 GB - enough to put a laptop into the OOM killer, with no
attacker involved, just a few big .log or .csv files.
Two bounds. The decoded text is cut to max-read at a rune boundary, so
the ceiling means what a reader takes it to mean. And extraction of
files at or above 4 MiB is rationed to two at a time, since holding
several large texts at once is what multiplies the ceiling; smaller
files, which is nearly all of them, are untouched.
twelve 40 MB files: peak RSS 3294 MB -> 728 MB, wall 27s -> 46s
two thousand small files: 0.05s both ways
The wall-clock cost falls entirely on large files needing extraction,
and buys a program that finishes instead of being killed.
comments that explain the code, not how it was written2026-09-17T10:11:42ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:11:42Zurn:sha1:bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd
About 340 comments cited the development process: task and plan
numbers, fix waves, rulings, reviewers, and the author in the third
person with a date. None of that exists outside the work itself, so to
a reader it pointed at nothing. Each one now states the engineering
reason it was standing in front of; where a comment was provenance and
nothing else, it is gone.
References to docs/design.md and docs/gui-design.md by section stay:
both ship with the repository. The design documents lose their
amendment diaries - CHANGELOG.md is that record - and the GUI's says
plainly that the window has gone further than the document.
Only comments changed. Every .go file was parsed and its code printed
with comments stripped, before and after: the two hashes are identical
across all 175 files.
docs: GUI design draft; code comments no longer name the owner2026-09-15T20:09:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:09:06Zurn:sha1:bbc9b103acac96b83b150b81f2effe1b65c3f8a2partial reads never cached; extractor version 3 discards 0.0.7 caches2026-09-14T22:27:13ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:27:13Zurn:sha1:fc6eda20555ea33f1a8260610056b7079c8e8fd9tests read real documents from LibreOffice and pandoc; antiword's short-document limit documented2026-09-14T22:02:37ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:02:37Zurn:sha1:8a046c897e42e9459aa99377589c80c773601efcbuild: VERSION checked for build and install, cross names without v, dependency gate covers tests and BSDs, tarball install, examples and extractor list tested2026-09-14T21:55:57ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:55:57Zurn:sha1:04f46bf180cf506ceadb76b5afacf9c02700cc65main excludes checked with the defaults' case and fold; Latin-1 decoding memory; hardlink election documented2026-09-14T21:53:54ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:53:54Zurn:sha1:0b155e8df3205aebf129091b517f4116665a5adccontent tests are three-valued: unknown when unreadable or read in part2026-09-14T21:39:37ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:39:37Zurn:sha1:c09020c2fb01da24d5befbed78ce3b73b5efbe4ctests run on OpenBSD; a tool's error message survives one large write; lock pids beyond 32 bits name no process2026-09-14T21:30:08ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:30:08Zurn:sha1:01b0cfe2055e23cf03870d9a9f60648037b4005etext that turns binary further on has no content, like an image2026-09-14T21:24:08ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:24:08Zurn:sha1:11a2c57c6eeaff0ef963fc6f8b74caa27b147bdb