Repository navigation
Promote staged fixes into 0.1.9 - #1827
Merged
Merged
Conversation
…spatch point's handlers, and starts at the producer - a registered callback that calls its own parameter (next) continues into what the same function registers after it on the same receiver, in order, with the registration line - a call through a value whose candidates exceed the fan cap names the registered handlers; the fan counts project, non-test candidates only - a question naming a producing verb (publish, send, forward...) that lands on the producing method starts at its caller; a caller joined only by name is one labelled step - a nested function's step names the factory that made it, read from spans Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
A producer that emits on a key (a Nest microservices client's emit/send, a
kafkajs producer's send({ topic })) was not joined to the handler registered
on the same key (@EventPattern / @MessagePattern, a kafkajs consumer's
subscribe), so path stopped at the send and impact of a handler named no
sender.
destinations.dl gains a messaging section. Both ends are recognised by the
receiver's DECLARED type and the package it is imported from (knobs.dl,
ts_msg_client_type), never by the method name, so emit on a Node event
emitter is not a send. The key is read the way a route is: a literal, a
const, a const-object member (now also through `as const`), local or
imported. One wrapper hop is bound: a private send(pattern, x) called with
the key joins from its caller. A decorator's Transport argument names the
broker; an end that names none joins any. One-sided keys are reported as
remote_unserved / remote_unsent, an unreadable key as remote_undetermined.
remote_unsent is judged by destination, so a handler reached by a send that
names no broker is not also reported unsent.
Checked: new CLI case cross-process-message (emit on an imported const-object
member, send on a const, a key through a wrapper, kafkajs send/subscribe,
controls: an EventEmitter emit and a handler nobody sends to) fails 5/7
before and passes 7/7; typescript case suite 212/212, engine suite 99/0. On a
monorepo with three services: probes 44 -> 47 of 74, no regression, call
edges unchanged, 5 amqp + 2 kafka remote edges added.
Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
`connection.model(name, schema)` builds the model class at runtime, so a call
such as `this.Doc.findLive()` on it had an untyped receiver and was only
matched by name, with same-named methods elsewhere as equal candidates.
The schema argument now gives the call a value: a `new Schema(...)` reached
through an import of the ORM package (named, default, namespace, require, or a
local destructure) is tracked, and whatever its `statics` holds (member
writes, `static('n', f)`, `static({...})`, the `statics` option) is a member
of every model made from it; its `methods` are members of `new Model(...)`.
The package's own members stay receiver_untyped as before.
Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
…ow-stops-at-dispatch-points
…factory-result-untyped
…w-stops-at-dispatch-points context: follow a middleware's next(), name a dispatch point's handlers, start at the producer
…broker-join typescript: join a message key's sender to its handler (remote_edge)
…actory-result-untyped javascript: a model made by an ORM factory carries its schema's statics
swapnilpaliwal-sd
requested review from
JaredHLZhang,
Whua689 and
suyashpaliwal26
as code owners
September 30, 2026 13:20
Contributor
Author
|
Scorecard after this promotion (probes on build 7400340; score = (3probes_failing + 2missed_dependents + 5precision_loss + agent_shortfalls + tokens_wasted/10k) * (1 + 0.25(apps_hit-1)))
Top 5 targets:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes 8 fixes from
apps/integration-0.1.9into0.1.9.Checked on the staged build: probes compared in 5 products (no regressions), end-to-end plugin/MCP/skill check passed.