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

   ### What changes were proposed in this PR?
   
   Build the expected dataset and model paths with Paths.get. Keep independent 
literal repository and commit values and exact generated-code equality. This 
repairs the Windows test expectation; production mounting is unchanged.
   
   ### Any related issues, documentation, discussions?
   
   Closes #8797
   
   ### How was this PR tested?
   
   On Windows: baseline one passed and one failed; patched two passed. An 
incorrect expected commit still failed exact equality. All 25 parameter tests 
and seven mount-manager tests passed; formatting and lint passed.
   
   ```text
   sbt "WorkflowOperator/testOnly 
org.apache.texera.amber.operator.udf.python.PythonUdfUiParameterSupportSpec 
org.apache.texera.amber.operator.udf.python.PythonUdfUiParameterInjectorSpec 
org.apache.texera.amber.operator.udf.python.UiUDFParameterSpec" 
"WorkflowCore/testOnly 
org.apache.texera.amber.storage.RepositoryMountManagerSpec" 
"WorkflowOperator/Test/scalafix --check" scalafmtCheckAll
   ```
   
   Localhost Chrome at 1707 by 979 ran File Scan to Python UDF with a scalar 
parameter and returned three exact lines. This does not test real FUSE mounts 
or Kubernetes.
   
   These local checks preceded today's rebase onto upstream main 98d3d4b1ec. 
Candidate changes are unchanged. Remote CI and the full operating-system matrix 
are not claimed.
   
   Test-only change. The screenshot checks unchanged UDF execution, not a real 
mounted dataset.
   
   ![Ordinary UDF 
compatibility](https://github.com/user-attachments/assets/5b11c0a9-b96f-42ae-820d-c1bd38e3fdfb)
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: OpenAI Codex (exact authoring version not recorded).
   


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