When a map is newly created from Python, we print the link to the map to the CLI. Seconds after creation, the map is almost never ready, and for a while we've relied on a redirect back to the dataset page. This has proven somewhat inconsistent. Instead, we should just link to the dataset page, where the user can see the current status of their map.
:rocket:
This description was created by Ellipsis for commit 6fe48ff36781ff4210df96e637fc2bc7a9f2e4f7
Summary:
Changed log message to use dataset link instead of map link, updated version in setup.py, and increased retry limit in test case.
Key points:
Updated nomic/dataset.py.
Modified nomic/dataset.py::AtlasDataset::create_index to log dataset link instead of map link.
Changed log message to use atlas_projection.dataset_link instead of atlas_projection.map_link.
Updated version in setup.py from 3.0.36 to 3.0.37.
Increased retry limit in tests/test_atlas_client.py::test_map_embeddings from 5 to 10.
When a map is newly created from Python, we print the link to the map to the CLI. Seconds after creation, the map is almost never ready, and for a while we've relied on a redirect back to the dataset page. This has proven somewhat inconsistent. Instead, we should just link to the dataset page, where the user can see the current status of their map.
Summary:
Changed log message to use dataset link instead of map link, updated version in setup.py, and increased retry limit in test case.
Key points:
nomic/dataset.py
.nomic/dataset.py::AtlasDataset::create_index
to log dataset link instead of map link.atlas_projection.dataset_link
instead ofatlas_projection.map_link
.setup.py
from3.0.36
to3.0.37
.tests/test_atlas_client.py::test_map_embeddings
from 5 to 10.Generated with :heart: by ellipsis.dev