kz930 opened a new pull request, #9060:
URL: https://github.com/apache/texera/pull/9060

   ### What changes were proposed in this PR?
   
   With results open beside their operators (#9058), the bottom panel drops its 
Result tab and keeps only the console.
   
   With no operator selected, the console shows every operator's messages in 
time order, each tagged with its operator; clicking a tag narrows it to that 
operator, as selecting the operator does. With one operator selected, it shows 
that operator's messages alone, under a line naming it that closes back to all. 
The errors from the Static Error tab join the console as error messages, shown 
by the rule the tab used: an operator's own errors with it, and errors that 
belong to no operator when none is selected. That tab and its component are 
removed.
   
   (screenshots)
   
   This needs #9058 and #9056, so the diff includes their commits, and #9054's, 
until they merge. The PR's own change is the last commit.
   
   ### Any related issues, documentation, discussions?
   
   Closes #9059. Part of #9052. Design discussed in #8842.
   
   ### How was this PR tested?
   
   The specs of the console, the console service and the result panel cover 
every operator's messages and their tags, narrowing to one operator and back, 
errors as console messages, and a re-render with an error present not moving 
the list. The full frontend suite passes. In the running app, two Python UDFs' 
prints and an error appear together, tagged by operator, and narrow to one 
operator when it is selected.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5.5)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to