@sjawhar/pi-envoy 16.15.0 → 16.17.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/envoy.js
CHANGED
|
@@ -41931,7 +41931,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
|
|
|
41931
41931
|
|
|
41932
41932
|
// package.json
|
|
41933
41933
|
var name = "@sjawhar/pi-envoy";
|
|
41934
|
-
var version2 = "16.
|
|
41934
|
+
var version2 = "16.17.0";
|
|
41935
41935
|
var package_default = {
|
|
41936
41936
|
name,
|
|
41937
41937
|
version: version2,
|
|
@@ -12,3 +12,4 @@ Read this in a Legion pane before you touch a role claim, or when a Legion role
|
|
|
12
12
|
- `receipt_timeout`: the listener forwarded the message to a live holder and no receipt arrived in time. The error names the holder. Its payload keeps `original_topic`, `event_id`, `payload` and the original `dedupe_key`, so the daemon can re-send it and the receiver's dedupe drops a copy that did arrive.
|
|
13
13
|
- A role message forwarded to you is kept on your inbox in the stream, which your own durable consumer reads, so your session gets it once, also after the pane restarts or reconnects.
|
|
14
14
|
- Never forward these failure payloads to an architect, because the daemon already acts on them.
|
|
15
|
+
- A role send the listener refuses `404` also raises one exception on `notifications.envoy.exceptions.notifications.role.<role>`, with the reason it refused: `unclaimed` or `holder_lapsed`. It is a bus signal and nothing more: no consumer acts on a peer's refusal, and the daemon's own refused outbox row retries by itself until the role is held or its architect cannot hold it again. Never re-send a refused message by hand on the strength of one.
|