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

   ### What changes were proposed in this PR?
   
   Manual backport of #7260 to `release/v1.2`, replacing #7389, whose head 
branch lives in this repository and so could not be corrected by push.
   
   The production half of the automated backport was already right: 
`TablesPlotOpDesc` and `FigureFactoryTableOpDesc` each define the 
`render_error` their generated `TableChartOperator` calls on two reachable 
branches, three lines apiece, exactly as on `main`.
   
   The tests were what failed. Neither operator has a descriptor spec on this 
branch, so the automation resolved the missing files by taking `main`'s whole, 
113 lines and 102 lines against the 11 apiece that #7260 actually added. What 
came along asserts on behaviour that is not on this branch: `main` passes a 
message to each `assert`, this branch does not, so 
`intercept[AssertionError](...).getMessage` is null and six of the fourteen 
tests fail. Those messages arrived in later PRs that were not backported, and 
this one should not carry them.
   
   Each spec here holds the one case #7260 added and the scaffolding it needs 
to run.
   
   ### Any related issues, documentation, discussions?
   
   Backport of #7260. Originally linked #7244. Replaces #7389, which can be 
closed.
   
   ### How was this PR tested?
   
   `WorkflowOperator/scalafmtCheckAll` and the two descriptor specs on this 
branch, 2 tests, both passing. For the record, the automated resolution was run 
on this branch first and failed 6 of 14: two `cannot be empty` cases per spec, 
plus `at least 30` and `non-negative` in `FigureFactoryTableOpDescSpec`.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 5)
   


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