local-fs mtime pinning breaks on uutils coreutils; readiness probe passes without honoring %3N width #23
Labels
No labels
component:adapters
component:lifecycle
component:qa
component:setup
component:shared
component:worktrees
phase/accepted
phase/backlog
phase/deployed
phase/developing
phase/integrating
phase/planning
phase/qa
phase/requirements
phase/uat
priority:critical
priority:critical
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:bug
type:chore
type:docs
type:feature
type:infra
type:tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jbr870/devwork-skills#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Spawned from finding
F-PO-21-3-1(pre-existing) on issue #21 during /develop (auto-applied disposition, developer-decidable).Observed: All four forge flow tests (
smoke.sh,disposition-flow.sh,promotion-flow.sh,release-flow.sh) die at pristine HEAD on a box whosedateis uutils coreutils 0.8.0:touch: Unable to parse date: @1786473805899219.616.local-fs/_lib.sh's_lfs_touch_msbuilds@epoch.fracfromdate +%s%3N, but uutils ignores the%3Nwidth and prints all nine nanosecond digits.The sharper defect: the readiness preflight for local-fs probes GNU date with a charset/length check that uutils passes without honoring the format — the guard reports ready on a box where the adapter cannot pin mtimes. The probe should verify the observed output length (13 chars for
%s%3Nseconds+millis), not just digits.Fix directions: (a) harden
_lfs_touch_msto truncate/normalize the fraction; (b) tighten the readiness probe per above. Either alone closes the observed failure; both close the class.This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run
/requirements --issue=<this>to flesh it out before planning.