Skip to content

[ZEPPELIN-6698] Verify EventBus note-removal browser parity - #5485

Closed
voidmatcha wants to merge 2 commits into
apache:masterfrom
voidmatcha:ZEPPELIN-6698-eventbus-parity
Closed

voidmatcha wants to merge 2 commits into
apache:masterfrom
voidmatcha:ZEPPELIN-6698-eventbus-parity

Conversation

@voidmatcha

@voidmatcha voidmatcha commented Sep 14, 2026

Copy link
Copy Markdown
Member

What is this PR for?

Verify that Job Manager receives the same note removal WebSocket payload in legacy and EventBus server modes.

This draft contains the ZEPPELIN-6340 server commit from PR #5441 because that prerequisite is not on master. After #5441 merges, this branch will be rebased so the final PR contains only the browser parity test and CI matrix.

What type of PR is it?

Improvement

Todos

What is the Jira issue?

ZEPPELIN-6698

How should this be tested?

cd zeppelin-web-angular
CI=true PLAYWRIGHT_HTML_OPEN=never ./node/npm run e2e -- --reporter=list tests/workspace/job-manager/eventbus-removal-parity.spec.ts
./node_modules/.bin/eslint e2e/tests/workspace/job-manager/eventbus-removal-parity.spec.ts
./node/npm exec prettier -- --check e2e/tests/workspace/job-manager/eventbus-removal-parity.spec.ts
cd ..
./mvnw test -pl zeppelin-server -Dtest=ZeppelinEventBusTest,NotebookServerTest#testEventBusHandlesNoteRemovedEvent -DfailIfNoTests=false

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

seung-00 and others added 2 commits September 14, 2026 23:44
Constraint: keep the check tied to the existing frontend E2E matrix and the new EventBus toggle.
Rejected: leave the workflow in one server mode because that would not compare the legacy and EventBus browser payloads.
Confidence: high
Scope-risk: frontend E2E runtime increases for the EventBus matrix.
Not-tested: full live Playwright run against a started Zeppelin server.
@voidmatcha voidmatcha closed this Sep 14, 2026
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