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

   ### What happened?
   
   The Tree Plot operator fails at runtime with `No module named 'igraph'` on a 
fresh
   install. Its generated Python template imports igraph 
(`TreePlotOpDesc.scala:75-76`),
   but igraph is not declared in any of the four Python dependency files
   (`amber/requirements.txt`, `amber/operator-requirements.txt`,
   `amber/dev-requirements.txt`, `amber/pyproject.toml`).
   
   `git grep -il igraph` on main returns exactly one file, 
`TreePlotOpDesc.scala` itself.
   A virtualenv built from the repository's requirements therefore never gets 
the package,
   so the operator can never run unless igraph is installed by hand.
   
   This looks like the same class of gap that `scikit-image` already has a note 
for in
   `amber/operator-requirements.txt`, except igraph is imported directly by the 
operator
   template rather than being an indirect runtime dependency of plotly.
   
   ### How to reproduce?
   
   1. Create a Python environment from the repository requirements and point
      `UDF_PYTHON_PATH` at it.
   2. Build a workflow of CSV File Scan into Tree Plot. Any input works, the 
operator
      fails before reading a row.
   3. Set Edge List Column to a column holding `[parent, child]` literals and 
run.
   4. The execution fails with `No module named 'igraph'`.
   
   Installing igraph into that environment makes the same workflow succeed, 
which
   confirms the missing declaration is the only cause.
   
   ### Version/Branch
   
   1.3.0-incubating-SNAPSHOT (main)
   
   ### Commit Hash (Optional)
   
   2c2c0e503
   
   ### What browsers are you seeing the problem on?
   
   Chrome
   
   ### Relevant log output
   
   ```shell
   java.lang.Throwable: java.lang.Throwable: No module named 'igraph'
   ```
   


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