[I] Machine Learning Scorer crashes with an empty KeyError when no Scorer Function is selected [texera]

["kz930 (via GitHub)" <gi...@apache.org>]

kz930 opened a new issue, #8302:
URL: https://github.com/apache/texera/issues/8302

   ### What happened?
   
   The Machine Learning Scorer operator has a Scorer Functions multi-select, which is empty when the operator is first dropped. Nothing marks it as required, so a workflow that leaves it untouched compiles and runs, and then fails inside the generated Python with `KeyError: ''`.
   
   The operator joins the selected metric names into a Python list literal. On an empty selection that literal comes out as `['']`, and the metric lookup is then asked for the empty name. The traceback points at the generated code rather than at the form field the user left blank, so nothing in the message says which of the operator's settings is missing.
   
   The same happens on both branches of the Regression switch, since each branch has its own metric list and both start empty.
   
   Expected: the operator is marked invalid in the editor until at least one metric is selected, the way any other required setting is.
   
   ### How to reproduce?
   
   Build a workflow of CSV File Scan feeding a Machine Learning Scorer. In the Scorer, leave Regression off, set Actual Value and Predicted Value to two columns holding the same labels, and leave Scorer Functions with nothing selected. Run the workflow. The Scorer fails with `KeyError: ''`.
   
   ### Version/Branch
   
   1.3.0-incubating-SNAPSHOT (main)
   
   ### Commit Hash (Optional)
   
   b59c7406d0a7
   


-- 
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: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Machine Learning Scorer crashes with an empty KeyError when no Scorer Function is selected [texera]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on issue #8302:
URL: https://github.com/apache/texera/issues/8302#issuecomment-5485791187

   <!-- texera:template-compliance -->
   👋 Thanks for opening this issue, @kz930!
   
   It looks like the issue description doesn't quite follow our template yet:
   
   - This issue doesn't appear to use one of our templates (Bug, Feature, or Task). Please open it using a template so the required details are captured.
   
   Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
   
   You can find the template prompts by editing the description, or see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the full contribution flow.
   


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Machine Learning Scorer accepts settings it cannot score and fails deep inside the generated Python [texera]

["aglinxinyuan (via GitHub)" <gi...@apache.org>]

aglinxinyuan closed issue #8302: Machine Learning Scorer accepts settings it cannot score and fails deep inside the generated Python
URL: https://github.com/apache/texera/issues/8302


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org