Skip to content

Default galaxy container fails to provide the environment for parse_parameter expression tool #447

@pcm32

Description

@pcm32

This one is a tricky one. Most "base" tools normally work with the same galaxy container, however the Expression tool parse_parameter fails because the container seems to lack node or nodejs:

Traceback (most recent call last):
  File "/galaxy/server/database/jobs_directory/012/12490/_evaluate_expression_.py", line 1, in <module>
    from galaxy_ext.expressions.handle_job import run; run()
  File "/galaxy/server/lib/galaxy_ext/expressions/handle_job.py", line 39, in run
    result = evaluate(None, inputs)
  File "/galaxy/server/lib/galaxy/tools/expressions/evaluation.py", line 12, in evaluate
    application = find_engine(config)
  File "/galaxy/server/lib/galaxy/tools/expressions/util.py", line 9, in find_engine
    raise Exception("nodejs or node not found on PATH")
Exception: nodejs or node not found on PATH

What would be the best way of dealing with this case? nodejs is surely in the container, so maybe inject an env var to modify the PATH somehow through tpv?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions