Forum Replies Created
-
AuthorPosts
-
June 10, 2022 at 2:42 pm in reply to: Using fabric-cli JSON output difficult (bug and/or feature request) #2101
fabric-cli currently does a json dump of the Slice object thus resulting in the escaping of the inner json objects. We would work on making this output more parseable in the next releases until then using the FABlib interface which returns the Python objects is recommended.
Current Fabric components are based on Python 3.9. Some of the underlying dependencies we are using are not available for Python 3.10 yet so upgrade to 3.10 doesn’t work.
-
This reply was modified 3 years, 8 months ago by
Komal Thareja.
I’ll add ipysheet in the default image with the next build. Also, you can restart your container from File -> Hub Control Panel -> Stop Container followed by Start Container.
Workaround to copy the following files seems to make conda happy. No luck finding the config parameter.
cp /opt/conda/conda-meta/certifi-2021.10.8-py39hf3d152e_2.json /opt/conda/conda-meta/certifi-2021.5.30-py39hf3d152e_0.json
cp /opt/conda/conda-meta/ca-certificates-2021.10.8-ha878542_0.json /opt/conda/conda-meta/ca-certificates-2021.5.30-ha878542_0.json-
This reply was modified 3 years, 9 months ago by
Komal Thareja.
By default ca-certificates.json exists and is not corrupted. After the first install using the conda, ca-certificates and certifi package gets updated. Even though ca-certificates and certifi packages were updated, conda still seems to be looking for older versions. Thus resulting in any subsequent install failures. I am looking at ways on how to reset conda to avoid such failures. In the meanwhile, could you please share the packages you need to install for your notebook? I can see if I can add them to the default notebook container image.
Snapshot before the install.

-
This reply was modified 3 years, 9 months ago by
Komal Thareja.
August 19, 2021 at 3:00 pm in reply to: Failed when adding two SharedNIC_ConnectX_6 to one node #748I am able to reproduce the error and found this to be a bug in the code. We would address it in the next release.
User should be able to get to the respective node components using the get_slice API:
`status, topology = slice_manager.get_slice(slice_id=slice_id)
if status == Status.OK:
print(f”Properties: {topology.nodes[‘n1’].list_properties()}”)
print(f”Components: {topology.nodes[‘n1’].components}”)
print(f”Component: {topology.nodes[‘n1’].components[‘c1’]}”)
else:
print(f”Failed to get slice topology: {topology}”)`However, I think we have bug which is preventing the components from being listed in the output of the above snippet.
-
This reply was modified 3 years, 8 months ago by
-
AuthorPosts
