Development record
refuseSymlinkedDir is defined twice with identical bodies, in internal/core/capture/reading.go and internal/core/readingitem/readingitem.go, since the reading-item locator moved into the readingitem leaf; two copies of the symlink guard are how two walks come to disagree about what the ledger contains. One primitive, in the leaf, with capture's call sites routed through it.
issueresolvedminoriss-2609251052592668
refuseSymlinkedDir is defined twice with identical bodies, in internal/core/capture/reading.go and internal/core/readingitem/readingitem.go, since the reading-item locator moved into the readingitem leaf; two copies of the symlink guard are how two walks come to disagree about what the ledger contains. One primitive, in the leaf, with capture's call sites routed through it.
Grounds
- pursued: capture's refusal of a symlinked directory is the leaf's primitive and carries both sentinels with the message unchanged; TestSymlinkGuardIsTheLeafs would fail if a second copy returned
Frontmatter
| id | iss-2609251052592668 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609251052592668-refusesymlinkeddir-is-defined-twice-with.md
open on GitHub ↗ · commit history ↗