version_workflow.go ×2

Frontier kind: Joint frontier

unlabeled · c_f41e2b6afff6

2 tests · 2943 LOC · 140 files · introduces 2 tests · 15 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges15 lines · 1 files
Tests
2 tests

Contains — complete concept membership

All code (extent)
470 ranges2943 lines · 140 files · Browse complete extent
All tests (intent)
2 testsBrowse 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.

2 tests introduced at this concept.

Introduced code

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

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

go.temporal.io/server/service/worker/workerdeployment/version_workflow.go 15 introduced LOC · 2 ranges

Open complete file

169 if d.VersionState.Status == enumspb.WORKER_DEPLOYMENT_VERSION_STATUS_DRAINED ||
170 d.VersionState.Status == enumspb.WORKER_DEPLOYMENT_VERSION_STATUS_INACTIVE {
172 > // Set up drainage info for monitoring
173 > d.VersionState.DrainageInfo = &deploymentpb.VersionDrainageInfo{
174 > Status: enumspb.VERSION_DRAINAGE_STATUS_DRAINING,
175 > LastChangedTime: timestamppb.New(workflow.Now(ctx)),
176 > LastCheckedTime: timestamppb.New(workflow.Now(ctx)),
177 > }
178 >
179 > // Use existing function to update status and sync to task queues
180 > d.updateVersionStatusAfterDrainageStatusChange(ctx, enumspb.VERSION_DRAINAGE_STATUS_DRAINING)
181 > d.syncSummary(ctx) // Notify parent deployment workflow of the status change
182 > d.setStateChanged() // Trigger CaN
183 > }
184 })
185 }
1202 case enumspb.VERSION_DRAINAGE_STATUS_DRAINED:
1203 d.VersionState.Status = enumspb.WORKER_DEPLOYMENT_VERSION_STATUS_DRAINED
1204 > case enumspb.VERSION_DRAINAGE_STATUS_DRAINING: version_workflow.go
1205 > d.VersionState.Status = enumspb.WORKER_DEPLOYMENT_VERSION_STATUS_DRAINING
1206 default:
1207 // This should only happen if we encounter an error while checking the drainage status of the version