Skip to content

build(mvp-multinode): hand asap-gorilla-go to the gorilla-merger build - #436

Merged
zzylol merged 1 commit into
mainfrom
feat/merger-intchunk-build-context
May 25, 2026
Merged

zzylol merged 1 commit into
mainfrom
feat/merger-intchunk-build-context

Conversation

@zzylol

@zzylol zzylol commented May 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Companion to ASAPQuery-backend #333 (gorilla-merger decode-on-read for cold intchunk value chunks). The merger now imports asap-gorilla-go/intchunk, which isn't in any published asap-gorilla-go tag, so its Dockerfile rewrites the asap-gorilla-go go.mod replace to point at a build-context. This change supplies that build-context from the in-repo monorepo checkout (${ROOT}/asap-gorilla-go) in build_images(), mirroring how data-plane's sibling path-deps and build_asap_otel.sh already inject local asap-gorilla-go. Also adds asap-gorilla-go to the required-build-inputs preflight.

Without this, the next gorilla-merger image build fails (the Dockerfile expects the asap-gorilla-go build-context).

Test plan

  • run_demo.sh build rebuilds asap/gorilla-merger:dev with the asap-gorilla-go build-context (compiles against intchunk)

…rger build

The gorilla-merger now imports the asap-gorilla-go intchunk subpackage (the cold
value-chunk codec behind the decode-on-read helper), which is not in any
published asap-gorilla-go tag. Pass the in-repo monorepo checkout to the build as
the `asap-gorilla-go` build-context (mirroring data-plane's sibling path-deps and
build_asap_otel.sh's replace); the merger Dockerfile rewrites its go.mod replace
to point at it. Also add asap-gorilla-go to the required-build-inputs check.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zzylol
zzylol merged commit 1c8e092 into main May 25, 2026
@zzylol
zzylol deleted the feat/merger-intchunk-build-context branch July 17, 2026 20:08
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