mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-11-15 02:49:33 +01:00
Codeman maintainer
37dfb73b1e
A subfolder whose bounded probe answered `unknown` came back as `children: []` with no `incomplete` and `truncated` false, so a dead mount, or a healthy one slower than the 1.5 s probe on first touch, read as an empty folder and a search missed it in silence. `unknown` is never `absent` (#516). Such a folder now goes on the walk's `unread` list, which flags the node and sets `truncated` in both walks. A folder the filesystem says is gone drops out quietly as before. The row said "file limit reached", which would be false here, so it now reads "Not fully scanned" for either reason. Reproduced on a real disk with a parent at mode 0444, where the child's stat answers EACCES: the API, the search and the panel all report it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Changesets
Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works
with multi-package repos, or single-package repos to help you version and publish your code. You can find
the full documentation for it in the repository.
What is a changeset?
A changeset is a piece of information about changes made in a branch or commit. It holds three bits of information:
- What packages need to be released
- What semver bump type each package should receive (major / minor / patch)
- A summary of the changes
How do I create a changeset?
Run npx changeset or create a .md file in this directory with the following format:
---
"codeman": patch
---
Description of changes
The frontmatter specifies which package(s) to bump and the bump type. The body is the changelog entry.