Development record
installDevShim silently swallows failures: the os.Remove, MkdirAll, and WriteFileAtomic error paths are bare returns (internal/core/ahoy/apply.go, installDevShim), so a failed shim write yields status=partial or clean with no note explaining what was not done or why; only the success path calls a.note
issueresolvedminoriss-227
installDevShim silently swallows failures: the os.Remove, MkdirAll, and WriteFileAtomic error paths are bare returns (internal/core/ahoy/apply.go, installDevShim), so a failed shim write yields status=partial or clean with no note explaining what was not done or why; only the success path calls a.note
Grounds
- pursued: every failed install write reaches the result as a note; shown wrong if a forced failure in any of these steps leaves the notes empty, which the dev_shim_failure tests force
Frontmatter
| id | iss-227 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-227-installdevshim-silently-swallows.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-2609120452369809Reported from a downstream repository using abcd: `abcd capture "<text>"` mints
- iss-2609260057127611Three ahoy install writes still swallow their errors, the class iss-227 fixed for their siblings: the identity pin (stepIdentityPin drops a failed identity.WritePin, and an unset git identity, without a word), the .gitignore visibility block (stepVisibility drops applyVisibilityBlock's error), and the conventions-file marker block (stepMarker drops installMarkerFile and removeMarkerFile failures). A run that wrote none of them reports with no reason.
- itd-111A Stale abcd Never Answers Silently