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
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>;
When the provisioner fails to provision a RunPod resource, the error messages produced by RunPod python package are unnecessarily verbose and confusing. For example:
Additionally, RunPod seems to hook into some exception printing methods, evidenced by:
Cc'ing @cblmemo for a look
The text was updated successfully, but these errors were encountered: