Skip to content

fix: support multiple foundational stores - #947

Closed
driescroons wants to merge 1 commit into
streamingfast:developfrom
driescroons:fix/multiple-foundational-stores
Closed

driescroons wants to merge 1 commit into
streamingfast:developfrom
driescroons:fix/multiple-foundational-stores

Conversation

@driescroons

Copy link
Copy Markdown

Problem

Modules can declare multiple foundational-store inputs, and the WASM runtimes assign each input its own index. The server only wired clients from the first input, so accessing index 1 failed with invalid foundational store index 1, 1 stores declared.

Fix

Wire exactly one client for each foundational-store input in declaration order. Reject unsupported client cardinality before execution instead of silently corrupting guest indexes.

Verification

  • go test ./pipeline/...
  • go vet ./pipeline/...
  • go build ./...
  • focused host index-routing tests
  • release-note validation
  • git diff --check

Co-authored-by: Cursor <cursoragent@cursor.com>
@driescroons
driescroons deleted the fix/multiple-foundational-stores branch September 18, 2026 01:15
@maoueh

maoueh commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Hey, was this an agentic mistake or something else?

Happy to update skills/docs if it was, to
avoid this for someone else.

Unless it's something else …?

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.

2 participants