Skip to content

fix: skip log viewer for partner app deploys - #74

Merged
jonoirwinrsa merged 4 commits into
mainfrom
fix/partner-deploy-no-log-viewer
Aug 11, 2026
Merged

fix: skip log viewer for partner app deploys#74
jonoirwinrsa merged 4 commits into
mainfrom
fix/partner-deploy-no-log-viewer

Conversation

@jonoirwinrsa

Copy link
Copy Markdown
Contributor

Summary

  • Partner services don't emit build logs, so the streaming log viewer was showing a misleading "Waiting for logs..." message and opening an unused websocket.
  • Build status polling already drives state for partner deploys, so the viewer is just removed for that path. Standard deploys are unchanged.

Test plan

  • Deploy a partner (e.g. deepgram/rime) app — no "Waiting for logs..." block appears; spinner shows "Building app..." until status reaches terminal.
  • Deploy a standard cortex/custom-runtime app — log viewer still streams build logs as before.
  • Run with --detach on a partner app — exits cleanly after create.

🤖 Generated with Claude Code

Partner services don't emit build logs, so creating the streaming log
viewer just produced a misleading "Waiting for logs..." message and
opened an unused websocket. Build status polling already drives the
state on its own.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jonoirwinrsa
jonoirwinrsa requested a review from wesrobin May 13, 2026 16:52
For partner deploys the app isn't ready when the build is accepted —
say "Build pending (ID: ...)" instead of "Created app (Build ID: ...)".
Standard flow wording is unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The appCreatedMsg partner branch had no live coverage: the only test over
it put its Msg in Finally(), which the harness never dispatches (Finally
only intercepts messages produced by a previous Step), so the subtest
never ran. Turn it into a real Step and add three partner cases:

- interactive: no log viewer is built and the view never shows the
  "Waiting for logs..." block
- simple output: prints the build-pending line and returns the status
  poll, which is the only thing driving the build to a terminal state
- detach: exits instead of polling

Each case asserts against a strict websocket mock, so re-introducing the
streaming viewer for partner deploys fails the test.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@jonoirwinrsa
jonoirwinrsa merged commit 65b6ef8 into main Aug 11, 2026
4 checks passed
@jonoirwinrsa
jonoirwinrsa deleted the fix/partner-deploy-no-log-viewer branch August 11, 2026 21:08
jonoirwinrsa added a commit that referenced this pull request Aug 12, 2026
## Problem

Partner service deploys skip file loading, zipping and upload entirely —
no local file is ever packaged. Validation demanded `main.py` anyway, so
a pure partner `cerebrium.toml` fails with `main.py not found` and the
user has to `touch main.py` to get past a check that never applies.

Hit while testing #74 against a real Deepgram deploy.

## Changes

- Exempt configs with a partner service from the `main.py` check in
`Validate`.
- Add `validator_test.go` covering partner-only, partner + custom
runtime, and the unchanged cortex cases.

## Verification

`go test ./...` and `go vet ./...` green. Confirmed against a real
project directory containing only `cerebrium.toml`: the pre-fix binary
exits 1 with `main.py not found`, this branch reaches the deployment
confirmation screen.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
jonoirwinrsa added a commit that referenced this pull request Aug 19, 2026
## Problem

Partner deploys skip loading, zipping and upload — they go straight from
create to build. The deploy checklist still rendered `Upload to
Cerebrium` as a pending step under `StateCreatingApp`, advertising a
stage that never runs. Same family as #74.

## Changes

- Skip the upload step line for partner services in `View()`.
- Assert the step is absent for partner deploys and still present for
standard ones.

## Verification

`go test ./...` and `go vet ./...` green; no golden files affected. The
spurious line is visible in the checklist captured from a real Deepgram
deploy while testing #74.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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