Package v0.2.12→v0.2.124: manifest, actions, version graph
This commit is contained in:
@@ -0,0 +1,13 @@
|
||||
import { VersionInfo } from '@start9labs/start-sdk'
|
||||
|
||||
export const v_0_2_91 = VersionInfo.of({
|
||||
version: '0.2.91:0',
|
||||
releaseNotes: {
|
||||
en_US:
|
||||
"Diagnostic logging for the pipelined-analyze window failures observed after v0.2.90 (5/6 windows still failing despite the mergeShortEntries fix — root cause unclear from rollup-only logs). v0.2.91 adds two new log lines per window: (1) at window READY-TIME: `[pipelined-analyze] window N/M: X segments → Y merged entries · time [aS-bS]` — shows segment count, post-merge entry count, and time range, so we can see if the merge is collapsing to a sensible density. (2) at window COMPLETE-TIME: `[pipelined-analyze] window N/M ok in Ts — K sections` on success OR `[pipelined-analyze] window N/M FAILED — <error>` on failure. The error string surfaces what analyzeOneWindow's MAX_ATTEMPTS=3 retry loop saw (invalid JSON, model 4xx, network, etc.) without grep-the-audit-DB. Next failed run should give us a concrete error string to diagnose.",
|
||||
},
|
||||
migrations: {
|
||||
up: async ({ effects }) => {},
|
||||
down: async ({ effects }) => {},
|
||||
},
|
||||
})
|
||||
Reference in New Issue
Block a user