You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few commands tend to err on the side of being a little too clean :)
e.g.
renku storage pull is great! But it shows no progress, so it's hard to tell what's happening
renku session start builds the image, but if there is an error in the image build it's not possible to see the reason
Example for the docker image build issue - this is the output from renku session start:
Ahhhhhhhh! You have found a bug. 🐞
1. Open an issue by typing "open";
2. Print human-readable information by typing "print";
3. See the full traceback without submitting details (default: "ignore").
Please select an action by typing its name (open, print, ignore) [ignore]:
Traceback (most recent call last):
File "/Users/rok/.venvs/renku-cli/bin/renku", line 8, in <module>
sys.exit(cli())
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/click/core.py", line 1137, in __call__
return self.main(*args, **kwargs)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/ui/cli/exception_handler.py", line 140, in main
self._handle_github()
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/ui/cli/exception_handler.py", line 172, in _handle_github
getattr(self, "_process_" + value)()
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/ui/cli/exception_handler.py", line 132, in main
return super().main(*args, **kwargs)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/ui/cli/exception_handler.py", line 91, in main
return super().main(*args, **kwargs)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/click/core.py", line 1062, in main
rv = self.invoke(ctx)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/click/core.py", line 1668, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/click/core.py", line 1668, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/click/core.py", line 763, in invoke
return __callback(*args, **kwargs)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/ui/cli/session.py", line 284, in start
session_start_command().with_communicator(communicator).build().execute(
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/command/command_builder/command.py", line 250, in execute
output = self._operation(*args, **kwargs) # type: ignore
File "pydantic/decorator.py", line 40, in pydantic.decorator.validate_arguments.validate.wrapper_function
from contextlib import _GeneratorContextManager
File "pydantic/decorator.py", line 134, in pydantic.decorator.ValidatedFunction.call
File "pydantic/decorator.py", line 206, in pydantic.decorator.ValidatedFunction.execute
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/core/session/session.py", line 144, in session_start
provider_api.build_image(project_context.dockerfile_path.parent, image_name, config)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/renku/core/session/docker.py", line 91, in build_image
self.docker_client().images.build(path=str(image_descriptor), tag=image_name)
File "/Users/rok/.venvs/renku-cli/lib/python3.9/site-packages/docker/models/images.py", line 285, in build
raise BuildError(chunk['error'], result_stream)
docker.errors.BuildError: The command '/bin/bash -c -o pipefail mamba env update -q -f /tmp/environment.yml && /opt/conda/bin/pip install -r /tmp/requirements.txt --no-cache-dir && mamba clean -y --all && mamba env export -n "root" && rm -rf ${HOME}/.renku/venv' returned a non-zero code: 1
which makes it immediately clear what needs to be addressed.
The default for both of these should probably be to show output so the user knows what is happening with the option to turn the output off (e.g. a -q flag or similar)
There are probably others...?
The text was updated successfully, but these errors were encountered:
A few commands tend to err on the side of being a little too clean :)
e.g.
renku storage pull
is great! But it shows no progress, so it's hard to tell what's happeningrenku session start
builds the image, but if there is an error in the image build it's not possible to see the reasonExample for the docker image build issue - this is the output from
renku session start
:and running
docker build
giveswhich makes it immediately clear what needs to be addressed.
The default for both of these should probably be to show output so the user knows what is happening with the option to turn the output off (e.g. a
-q
flag or similar)There are probably others...?
The text was updated successfully, but these errors were encountered: