The GitHub Actions job "Required Checks" on texera.git/feat/sklearn-config-constraints has succeeded. Run started by GitHub user kz930 (triggered by kz930).
Head commit for run: 1134fd8e95620c0f6c2dc09c01ae35a6e372b054 / kary zheng <[email protected]> feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit Two configurations ended the run with an error from inside scikit-learn or from code generation, naming neither the column nor the field to change. The text column now states what it takes. Count Vectorizer tokenizes documents, so the column is a string, and it is required exactly when that switch is on: with the switch off nothing reads it, and with the switch on a blank one reached code generation as a null and became #EXCEPTION DURING CODE GENERATION. Both are schema constraints, the second in the conditional form Aggregate already uses, so the panel refuses the configuration while it is being written. Conditional rather than a plain required, so a freshly dropped operator, whose vectorizer is off, is not flagged for a field it has no use for. The feature set drops what it cannot fit rather than ending the run. These operators take every column but the target, so a text column beside the numbers, one the user never meant as a feature, raised ValueError: could not convert string to float, and a timestamp raised DTypePromotionError. Nothing in the configuration could exclude it and the message named neither the column nor a way out. Booleans are kept, fitting as 0/1. What was left out is printed, so the choice is visible rather than silent, and this follows the rest of the codebase, where twenty-four visualization operators drop missing values before plotting. The drop is skipped under the text pipeline, where X is one string column by construction and filtering would empty it. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/31754712491 With regards, GitHub Actions via GitBox
