Repository navigation
[ZEPPELIN-6742] Connect the Assistant frontend to conversation REST and WebSocket APIs - #5563
Open
voidmatcha wants to merge 2 commits into
Conversation
voidmatcha
changed the base branch from
temp/seung-00/assistant-transport-base
to
branch-seung-00-assistant-transport-base-temp
October 9, 2026 01:35
voidmatcha
force-pushed
the
voidmatcha/assistant-v2-6-transport
branch
2 times, most recently
from
October 9, 2026 09:09
2aaa236 to
b75de05
Compare
voidmatcha
changed the base branch from
branch-seung-00-assistant-transport-base-temp
to
branch-seung-00-assistant-transport-clean-temp
October 9, 2026 09:09
voidmatcha
force-pushed
the
voidmatcha/assistant-v2-6-transport
branch
from
October 9, 2026 09:13
b75de05 to
c470802
Compare
Member
Author
|
This PR connects the frontend to the conversation REST API and WebSocket run events. After a connection loss, the user can reload saved history; the transport does not require a server-side The current diff is +1,460/-1 across four files. Excluding the 800 lines of tests, the review diff is +660/-1. There is no lockfile change. This PR depends on #5547, #5558, and #5561. Its temporary base contains those prerequisites without the separate server fixes. Reviews can proceed against this diff; after the prerequisites merge, I will rebase and retarget the PR to |
voidmatcha
force-pushed
the
branch-seung-00-assistant-transport-clean-temp
branch
from
October 10, 2026 00:50
b772a8d to
9f119fc
Compare
voidmatcha
force-pushed
the
voidmatcha/assistant-v2-6-transport
branch
from
October 10, 2026 00:50
0c3b303 to
c41de73
Compare
voidmatcha
force-pushed
the
branch-seung-00-assistant-transport-clean-temp
branch
from
October 10, 2026 08:27
9f119fc to
b0b71a0
Compare
voidmatcha
force-pushed
the
voidmatcha/assistant-v2-6-transport
branch
from
October 10, 2026 08:27
c41de73 to
3af8991
Compare
voidmatcha
force-pushed
the
branch-seung-00-assistant-transport-clean-temp
branch
from
October 10, 2026 08:37
b0b71a0 to
fc57755
Compare
voidmatcha
force-pushed
the
voidmatcha/assistant-v2-6-transport
branch
from
October 10, 2026 08:37
3af8991 to
3bcb8e2
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this PR for?
Connect the Assistant frontend to the conversation REST and WebSocket APIs. The transport provides conversation creation and retrieval, message sending, and response delivery for the UI.
This PR depends on server PR #5547, shared prerequisites #5558, and UI contracts #5561. Its temporary base contains exactly those changes. After a WebSocket disconnect, the transport shows an uncertain run state until the user reloads the saved history; it does not require a server-side
runningfield.What type of PR is it?
Feature
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-6742
How should this be tested?
Run from
zeppelin-web-angular/:npm run build-project:sdk npm run typecheck:react npm --prefix projects/zeppelin-react test -- src/entities/assistant/model/assistantTransport.spec.tsAlso verify the REST and WebSocket integration against the final API contract from server PR #5547.
Screenshots (if appropriate)
N/A
Questions: