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
Increasing minimum cluster size causes nodes/clusters to disappear as expected but decreasing doesn't cause them to reappear as expected. Instead, minimum cluster size must be set to 1 to get them to reappear.
Under the hood, it looks like when a cluster is hidden through minimum cluster size, the cluster is split such that each of those nodes is now a singleton (1 node cluster). Therefore, by setting minimum cluster size back to 1 the singletons reappear and are joined back together in the cluster. This splitting shouldn't occur and is the reason for the bug.
The text was updated successfully, but these errors were encountered:
dacowan404
changed the title
Decreasing minimum cluster size doesn't cause nodes/cluster to reappear as expected
Angular: Decreasing minimum cluster size doesn't cause nodes/cluster to reappear as expected
Jan 3, 2025
dacowan404
added a commit
to mossy426/MicrobeTrace
that referenced
this issue
Jan 6, 2025
removed code that called tagClusters function when minimum cluster size was updated. This function led to the splitting of cluster that were less than minimum. deployed to mossy url 1/6/25
Increasing minimum cluster size causes nodes/clusters to disappear as expected but decreasing doesn't cause them to reappear as expected. Instead, minimum cluster size must be set to 1 to get them to reappear.
Under the hood, it looks like when a cluster is hidden through minimum cluster size, the cluster is split such that each of those nodes is now a singleton (1 node cluster). Therefore, by setting minimum cluster size back to 1 the singletons reappear and are joined back together in the cluster. This splitting shouldn't occur and is the reason for the bug.
The text was updated successfully, but these errors were encountered: