registry.go ×4

Frontier kind: Code frontier

unlabeled · c_327abb287989

23 tests · 2163 LOC · 107 files · introduces 0 tests · 18 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
4 ranges18 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
324 ranges2163 lines · 107 files · Browse complete extent
All tests (intent)
23 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.

No tests are introduced at this concept. Its intent tests are introduced by other concepts.

Introduced code

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

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

go.temporal.io/server/service/history/workflow/update/registry.go 18 introduced LOC · 4 ranges

Open complete file

329 includeAlreadySent bool,
330 workflowTaskStartedEventID int64,
331 > ) []*protocolpb.Message { registry.go
332 > var outgoingMessages []*protocolpb.Message
333 >
334 > // TODO (alex-update): currently sequencing_id is simply pointing to the
335 > // event before WorkflowTaskStartedEvent. SDKs are supposed to respect this
336 > // and process messages (specifically, updates) after event with that ID.
337 > // In the future, sequencing_id could point to some specific event
338 > // (specifically, signal) after which the update should be processed.
339 > // Currently, it is not possible due to buffered events reordering on server
340 > // and events reordering in some SDKs.
341 > sequencingEventID := &protocolpb.Message_EventId{EventId: workflowTaskStartedEventID - 1}
342 >
343 > // Sort Updates by the time they were admitted to send them in deterministic order.
344 > var sortedUpdates []*Update
345 > for _, upd := range r.updates {
346 sortedUpdates = append(sortedUpdates, upd)
347 }
348 > slices.SortStableFunc(sortedUpdates, func(u1, u2 *Update) int { return u1.admittedTime.Compare(u2.admittedTime) }) registry.go
349
350 > for _, upd := range sortedUpdates { registry.go
351 outgoingMessage := upd.Send(includeAlreadySent, sequencingEventID)
352 if outgoingMessage != nil {
355 }
356
357 > return outgoingMessages registry.go
358 }
359