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 canceling (or getting an exception) during feat/umap, that gets cached for subsequent runs. We expect them to be not cached, e.g., recomputed, on future runs.
To Reproduce
Expected behavior
The caching flow should catch the interrupt/exn, ensure no caching, and rethrow.
Actual behavior
Screenshots
Browser environment (please complete the following information):
Graphistry GPU server environment
PyGraphistry API client environment
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
When canceling (or getting an exception) during feat/umap, that gets cached for subsequent runs. We expect them to be not cached, e.g., recomputed, on future runs.
To Reproduce
Expected behavior
The caching flow should catch the interrupt/exn, ensure no caching, and rethrow.
Actual behavior
Screenshots
Browser environment (please complete the following information):
Graphistry GPU server environment
PyGraphistry API client environment
Additional context
The text was updated successfully, but these errors were encountered: