Skip to content

fix(cache): wait for packed manifest discovery - #9

Merged
cre4ture merged 1 commit into
mainfrom
codex/pack-startup-timeout
Aug 17, 2026
Merged

cre4ture merged 1 commit into
mainfrom
codex/pack-startup-timeout

Conversation

@cre4ture

Copy link
Copy Markdown
Owner

Summary

  • use the configured backend timeout while packed manifests are discovered before the cache server becomes ready
  • retain the short 15-second startup check for object mode
  • document the shared deadline, test the mode-specific behavior, and rebuild the v0.3.1 artifacts

Why

A real IronMesh cache seed currently contains 172 PAC manifests. The first read-only restore correctly discovers them before listening, but v0.3.0's Action wrapper stopped waiting after 15 seconds. This change lets the wrapper wait for the same bounded timeout that the server already uses for discovery, preventing false startup failures and early cache misses.

Validation

  • node --test action/*.test.js
  • go test ./...
  • go vet ./...
  • staticcheck, govulncheck, and actionlint
  • rebuilt v0.3.1 distributions; checksums verified and a second build was byte-identical

@cre4ture
cre4ture merged commit d648e13 into main Aug 17, 2026
4 checks passed
@cre4ture
cre4ture deleted the codex/pack-startup-timeout branch August 17, 2026 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant