Vihren Atlas

registry.go ×3

Joint frontier

unlabeled · c_9d9b292714d8

1 test · 8518 LOC · 252 files · introduces 1 test · 18 LOC · 3 files

Introduces — evidence that enters the hierarchy at this concept

Code
5 ranges18 lines · 3 files
Tests
1 test

Contains — complete concept membership

All code (extent)
1841 ranges8518 lines · 252 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.

3 files ranked by introduced lines: 18 introduced LOC across 5 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/api/respondworkflowtaskcompleted/workflow_task_completed_handler.go 11 introduced LOC · 1 range

Open complete file

256
257 if len(rejectedUpdateIDs) > 0 {
258 > handler.logger.Warn( workflow_task_completed_handler.go
259 > "Workflow task completed w/o processing updates.",
260 > tag.WorkflowNamespaceID(wfKey.NamespaceID),
261 > tag.WorkflowID(wfKey.WorkflowID),
262 > tag.WorkflowRunID(wfKey.RunID),
263 > tag.WorkflowEventID(workflowTaskScheduledEventID),
264 > tag.String("worker-identity", workerIdentity),
265 > tag.Strings("update-ids", rejectedUpdateIDs),
266 > tag.Int("rejected-count", len(rejectedUpdateIDs)),
267 > )
268 > }
269
270 // At this point there must not be any updates in a Sent state.
go.temporal.io/server/service/history/workflow/update/registry.go 4 introduced LOC · 3 ranges

Open complete file

302 for _, upd := range r.updates {
303 if upd.isSent() {
304 > updatesToReject = append(updatesToReject, upd) registry.go
305 > }
306 }
307
308 var rejectedUpdateIDs []string
309 for _, upd := range updatesToReject {
310 > if err := upd.reject(unprocessedUpdateFailure, effects); err != nil { registry.go
311 return nil
312 }
313 > rejectedUpdateIDs = append(rejectedUpdateIDs, upd.id) registry.go
314 }
315 return rejectedUpdateIDs
go.temporal.io/server/common/log/tag/zap_tag.go 3 introduced LOC · 1 range

Open complete file

172 }
173
174 > func Strings(key string, value []string) ZapTag { zap_tag.go
175 > return NewStringsTag(key, value)
176 > }
177
178 func Stringer(key string, value fmt.Stringer) ZapTag {

Direct hierarchy

Children