Commit 574a0a5
committed
itest: boot piri on Postgres so the stack comes up
Every top-level itest — TestForgeVersity, TestForgeScenarios,
TestForgeNativeProvision, TestForgeReadAfterEviction — failed at stack
boot, not in any assertion:
Error: initializing piri node: ... ProvideHarmonyDB ...
curio PDP pipeline requires Postgres (set database type to postgres)
Since piri:main absorbed Curio (~2026-07-24) its PDP pipeline refuses
sqlite, and forgeStack booted sqlite piri via the zero-value
PiriNodeConfig. All four suites route through that one constructor, so
flipping the topology default to Postgres:true is the whole fix; the
pinned smelt already supports it (no dependency bump).
Also relax the CORS preflight status assertion from 200 to any 2xx, the
fetch spec's 'ok status' range. versitygw answers a matched rule 200 and
only its no-CORS-config fallback 204, and the Max-Age assertion is what
actually pins the real path: the fallback sets no Max-Age and mirrors the
requested method instead of the rule's method list. This supersedes the
exact-200 assertion in 900d6b5.
Both changes match what #44 arrived at independently, so the overlap
resolves trivially whichever lands first.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017rwJ8KiPhm3G27vfU21Phk1 parent 900d6b5 commit 574a0a5
2 files changed
Lines changed: 10 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
290 | 290 | | |
291 | 291 | | |
292 | 292 | | |
293 | | - | |
294 | | - | |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
295 | 298 | | |
296 | | - | |
297 | | - | |
| 299 | + | |
| 300 | + | |
298 | 301 | | |
299 | 302 | | |
300 | 303 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
104 | 104 | | |
105 | 105 | | |
106 | 106 | | |
107 | | - | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
108 | 110 | | |
109 | 111 | | |
110 | 112 | | |
| |||
0 commit comments