Repository navigation
feat(frontend): explain the Kill button and where to find results and errors - #8771
Merged
Xiao-zhen-Liu merged 5 commits intoNov 7, 2026
Merged
Conversation
… errors - Kill button: tooltip "Stop this run. A stopped run can't be resumed." - Result panel empty state: say to click an operator for its results and Console, or an empty spot on the canvas for all operators' errors (the Static Error tab only appears when nothing is selected) Refs TEX-86 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 94dff2f)
Contributor
Automated Reviewer SuggestionsBased on the
|
Contributor
Author
|
/request-review @Xiao-zhen-Liu |
- Errors an operator hits while running pause the run and show in its Console; the Static Error tab only appears when the run fails. Say that instead of "click an empty spot to see errors from all operators". - Show "Click an operator..." only when nothing is selected, and no click hints while previewing a workflow version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Fixed: the selection hint disappears once an operator is selected, and both new hints are hidden during version preview. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8771 +/- ##
=========================================
Coverage 92.32% 92.33%
- Complexity 5045 5048 +3
=========================================
Files 1260 1260
Lines 54026 54034 +8
Branches 6744 6746 +2
=========================================
+ Hits 49879 49891 +12
+ Misses 2487 2485 -2
+ Partials 1660 1658 -2
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…and say why the panel is empty - A Python UDF that fails while starting reports its error from the coordinator, so the error says "unknown operator" and clicking the UDF showed only an empty Console. When an operator is selected, the Static Error tab now also shows errors that are not tied to any operator on the canvas (shared errorsForOperator filter used by the result panel and the error frame). - The empty Result tab now says why it is empty: "No operator is selected." or "This operator has no results yet." Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sshiv012
pushed a commit
to sshiv012/texera
that referenced
this pull request
Oct 15, 2026
- Result panel: the empty states now say "No operator is selected" or "This operator has no results yet"; clicking a failed box shows its Static Error tab (apache#8771). - UDF guide: new rows for "does not implement <method>" and "does not subclass a pytexera base class", @OVERRIDES on a helper, the "(NameError at line 2 of the UDF code)" format, and "Columns" for 1-out UDFs (apache#8768, apache#8769). - Retake errors-all-operators.png with the final message, on a Texera built from all five code PRs on current main. Refs apache#8736 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t panel Showing errors that are not tied to any operator under whichever operator is clicked is too broad. The startup error of a failed UDF should instead carry the failing worker's operator id from the backend; that fix will be a separate PR. This PR keeps the per-case empty-state headings and hints. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Xiao-zhen-Liu
approved these changes
Oct 21, 2026
Xiao-zhen-Liu
enabled auto-merge
October 21, 2026 19:09
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Oct 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Oct 22, 2026
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 changes were proposed in this PR?
Two small hints in the workspace:
Before and after, with nothing selected (top) and an operator selected (middle). The bottom row (a failed UDF showing its Static Error tab when clicked) is no longer part of this PR: on main that error still arrives as "unknown operator", because
ControlErrordrops the worker that #8668 attaches. That will be fixed in the backend in a separate PR.The tooltip is a native
title, which browsers don't draw in screenshots. I checked it in the running app: hovering the red button shows "Stop this run. A stopped run can't be resumed."Any related issues, documentation, discussions?
Part of #8736. Split out of #8737.
How was this PR tested?
New specs in
result-panel.component.spec.ts(nothing selected, an operator selected, version preview) andmenu.component.spec.ts(the tooltip).Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5.5)