Skip to content

[ZEPPELIN-6671] Add execution streaming fixtures - #5482

Draft
voidmatcha wants to merge 2 commits into
apache:masterfrom
voidmatcha:ZEPPELIN-6671-execution-streaming-fixtures
Draft

voidmatcha wants to merge 2 commits into
apache:masterfrom
voidmatcha:ZEPPELIN-6671-execution-streaming-fixtures

Conversation

@voidmatcha

@voidmatcha voidmatcha commented Sep 14, 2026 •

Copy link
Copy Markdown
Member

What is this PR for?

Capture and replay execution streaming, disabled streaming, and cancellation traffic with build provenance. The tests validate complete fixtures and reject incompatible or incomplete captures.

What type of PR is it?

Improvement

Todos

  • Add isolated capture build provenance
  • Add execution and cancellation fixtures
  • Add replay and fixture validation

What is the Jira issue?

ZEPPELIN-6671

How should this be tested?

cd zeppelin-web-angular
npm run check:core-contract-fixtures

Screenshots (if appropriate)

Not applicable.

Questions:

  • Does the license files need to update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? Yes - Capture and replay commands are documented in the core-contract README

@voidmatcha voidmatcha closed this Sep 14, 2026
@voidmatcha voidmatcha reopened this Sep 27, 2026
@voidmatcha
voidmatcha force-pushed the ZEPPELIN-6671-execution-streaming-fixtures branch from fbfab00 to ad84ee1 Compare September 27, 2026 14:27
@voidmatcha

voidmatcha commented Sep 27, 2026 •

Copy link
Copy Markdown
Member Author

This is a child of ZEPPELIN-6665 and builds on the fixture format from #5458 (ZEPPELIN-6666). The notebook migration moves execution handling into the Shared Notebook Core and the React remote. To test that code against what the server actually sends, without starting a server, this PR records execution, streaming and cancellation traffic from an origin/master build and replays it.

@voidmatcha

voidmatcha commented Sep 27, 2026 •

Copy link
Copy Markdown
Member Author

#5486 changes how paragraph output is delivered, so I will recapture the fixtures from origin/master after it is merged and then mark this PR ready for review. Until then I will keep it as a draft.

Prune VCS and frontend toolchain directories from the launcher fallback WAR
search so it cannot select artifacts that capture-build-manifest intentionally
excludes. Exercise the real launcher search from the manifest regression test.

Confidence: high
Scope-risk: Custom deployments storing WAR files beneath node or node_modules
  are no longer discovered by fallback search.
Not-tested: Full core-contract suite requires Playwright and webpack
  dependencies unavailable in the clean worktree.
Signed-off-by: YONGJAE LEE <dev.yongjaelee@gmail.com>

This branch has not been deployed

No deployments
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