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
While running the CLI, not having tensorboard installed in my current environment repeatedly produces an error on many of the CLI pages. Maybe the presence/absence of python packages can be detected ahead of time to avoid unintentional errors being displayed.
Example view:
▶ Choose a Plan
<string> 1 <module>"<string>", line 1
NameError:
name 'tensorboard' is not defined
# CLI output continues here...
MacOS, installed via Brew, version 0.0.17.
The text was updated successfully, but these errors were encountered:
I didn't see an option for GLUE. I selected BERT, the only option, and training (not fine-tuning). I wasn't running anything in the background -- do I need to run a supporting program?
Here's the full output from repeating the same steps.
Additionally, when creating COS keys I errored out. This is a separate bug, but I'll keep it in this issue for now.
Thanks again.
✔ Choice 8: Choose a Plan · Lite
✖ Expanding IBM Cloud Object Storage Service Keys
✖ Expanding IBM Cloud Object Storage Service Keys
--------------------------------------------------------------------------------------------------------------
<string> 1 <module>
"<string>", line 1
>
NameError:
name 'tensorboard' is not defined
▶ Choose a Plan
ibmcloud resource service-instance-create ${S3_SERVICE} cloud-object-storage Lite global
FAILED
No resource group targeted. Use 'ibmcloud target -g RESOURCE_GROUP' to target a resource group.
ibmcloud resource service-instance-create ${S3_SERVICE} cloud-object-storage Lite global failed
While running the CLI, not having
tensorboard
installed in my current environment repeatedly produces an error on many of the CLI pages. Maybe the presence/absence of python packages can be detected ahead of time to avoid unintentional errors being displayed.Example view:
MacOS, installed via Brew, version 0.0.17.
The text was updated successfully, but these errors were encountered: