Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pcm32 opened this issue Oct 27, 2023 · 1 comment

Comments

@pcm32
Copy link
Member

pcm32 commented Oct 27, 2023

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?

@pcm32
Copy link
Member Author

pcm32 commented Oct 27, 2023

Probably just using a nodejs won't do, as it needs the galaxy parts as well. Maybe a new container FROM the main galaxy one with nodejs installed on top? For the meantime I mean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant