Problem
When using the two-step flow (create-env → cardano --node-env), genesis timestamps become stale between the two invocations. create-env writes start times as now + 15s, but by the time cardano --node-env runs, those times are in the past. The default for updateTimestamps is DontUpdateTimestamps, so unless the user explicitly passes --update-time, the testnet may fail to start.
In the direct cardano path (no --node-env), this is not a problem because createTestnetEnv and cardanoTestnet run back-to-back in the same process.
Proposed fix
In Parsers/Run.hs, in the UserProvidedEnv branch of runCardanoOptions, pass conf{updateTimestamps=UpdateTimestamps} as the default. Consider adding a --no-update-time flag for opt-out.
This is a 1-line change. Updating already-fresh timestamps is harmless (just shifts them by ~15s).
Type: Consistency fix
Effort: Trivial (1 line)
Risk: Very low
Problem
When using the two-step flow (
create-env→cardano --node-env), genesis timestamps become stale between the two invocations.create-envwrites start times asnow + 15s, but by the timecardano --node-envruns, those times are in the past. The default forupdateTimestampsisDontUpdateTimestamps, so unless the user explicitly passes--update-time, the testnet may fail to start.In the direct
cardanopath (no--node-env), this is not a problem becausecreateTestnetEnvandcardanoTestnetrun back-to-back in the same process.Proposed fix
In
Parsers/Run.hs, in theUserProvidedEnvbranch ofrunCardanoOptions, passconf{updateTimestamps=UpdateTimestamps}as the default. Consider adding a--no-update-timeflag for opt-out.This is a 1-line change. Updating already-fresh timestamps is harmless (just shifts them by ~15s).
Type: Consistency fix
Effort: Trivial (1 line)
Risk: Very low