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

[UX] RunPod Package Produces Messy and Unclear Output During Failures #4606

Open
andylizf opened this issue Jan 25, 2025 · 0 comments
Open

Comments

@andylizf
Copy link
Contributor

andylizf commented Jan 25, 2025

When the provisioner fails to provision a RunPod resource, the error messages produced by RunPod python package are unnecessarily verbose and confusing. For example:

ERROR  | Uncaught exception | <class 'RuntimeError'>; Failed to SSH to 104.143.3.149 after timeout 600s, with Error: ConnectionRefusedError: [Errno 111] Connection refused; <traceback object at 0x79d58dad6c00>;

Additionally, RunPod seems to hook into some exception printing methods, evidenced by:

>>> import runpod
>>> runpod.runpod.cli.groups.ssh.functions.add_ssh_key('qwq')
ERROR  | Uncaught exception | <class 'AttributeError'>; module 'runpod' has no attribute 'runpod'; <traceback object at 0x7f26fa689940>;

Cc'ing @cblmemo for a look

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