Vihren Atlas

tree.go ×1

Joint frontier

unlabeled · c_d60e446def2c

1 test · 2827 LOC · 99 files · introduces 1 test · 19 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
1 range19 lines · 1 files
Tests
1 test

Contains — complete concept membership

All code (extent)
575 ranges2827 lines · 99 files · Browse complete extent
All tests (intent)
1 testBrowse complete intent

Neighbourhood graph

The orange circle is the focus. Violet and green circles are every ancestor and descendant, broader and narrower, at any distance; blue squares and pink diamonds are the introduced files and exact introduced tests of every visible concept, not only the focus's. Arrows point from broader to narrower concepts and bridge only concepts omitted from this view. Undirected links show source or test introduction. Concept and file size follows LOC; exact test nodes use test-count units.

Introduced files, introduced tests, and structurally relevant concept specialization

In the embedded map, ordinary wheel input scrolls the page; use the visible controls to zoom and drag to pan. Open the full-screen map for canvas navigation: wheel pans, Ctrl/Command plus wheel zooms, and arrow keys pan when this region is focused. On touch screens, open the full-screen map to pan or pinch. If JavaScript or WebGL is unavailable, use the native relationship evidence on this page.

Graph controls are ready.

Interactive rendering requires JavaScript and WebGL. Use the native relationship evidence on this page while the interactive map is unavailable.

Native relationship evidence

Every exact file and test below is linked only from the concept that introduces it.

Introduced tests

Every collected test enters the hierarchy at exactly one concept.

1 test introduced at this concept.

Introduced code

Every collected source range enters the hierarchy at exactly one concept.

1 file ranked by introduced lines: 19 introduced LOC across 1 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/chasm/tree.go 19 introduced LOC · 1 range

Open complete file

2786
2787 if node == n.root() {
2788 > // Root node can never be deleted tree.go
2789 > // This can happen when:
2790 > // 1. CHASM framework is disabled in source cluster and sends an
2791 > // empty snapshot to the standby cluster. If the standby cluster
2792 > // has a non-empty chasm tree, the root node will be marked for
2793 > // deletion and we will lose archetype information for the execution,
2794 > // and hit other undefined issues when root is deleted.
2795 > // Disabled CHASM framework itself is already an undefined situation
2796 > // for non-workflow chasm executions, and we are ok with not deleting
2797 > // the root node.
2798 > //
2799 > // 2. CHASM is enabled but the execution is a workflow which doesn't
2800 > // have any chasm nodes. In this case, again an empty snapshot will be sent to
2801 > // standby cluster.
2802 > // In this case, we can actually choose to delete the root itself because empty
2803 > // chasm tree is assume to be a Workflow. However, given chasm workflow component's
2804 > // state is an empty proto, skipping deletion is fine as well. All other child nodes
2805 > // will still be deleted.
2806 > continue
2807 }
2808

Direct hierarchy

Children