novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
2,779 Commits 47 Branches 0 Tags
8e402c82bfb201626002c3b7737d950400c9b02c
Commit Graph
12 Commits
Author SHA1 Message Date
jschoubben 8e402c82bf Pin mesh-sdk 2da0de7, the release's final head, in the modules the release changes (issue 774)
mesh/delivery ready: it is merged on the Approve
Details
mesh/check checking 8e402c82bfb2 on 12c2574c9d54 | novox/mesh-catalog#560 in group feat/774-l3-reland
mesh/delivery-group group feat/774-l3-reland checking: the checker's verdict is out of date: novox/mesh-catalog@8e402c82bfb2 was judged on trunk f61265f7a0f3, …
Details
2026-10-30 01:15:38 +01:00
jschoubben 9cb177cae6 Pin mesh-sdk 6e4a301 in the modules the release changes, and keep the others on their pins (issue 774) 2026-10-30 00:23:45 +01:00
jschoubben 1b16720030 Pin mesh-sdk 007b6fd, the release's final head (issue 774) 2026-10-30 00:10:13 +01:00
jschoubben c1eb7783e8 Pin the newest mesh-sdk in the modules of the leaves (issue 1955) 2026-10-30 00:02:39 +01:00
jschoubben 1f0ff6ed98 Every offer of twenty providers says its credential form; a check refuses one that does not; re-pin sdk 6b8c694 (issue 1952) 2026-10-29 22:49:41 +01:00
jschoubben 8fac0f89f7 Re-pin the release sdk; the nats tools' secret directory is /var/lib/mesh/nats-tools (issue 1952) 2026-10-29 22:01:47 +01:00
jschoubben 9ccb6f4060 Re-pin the release sdk; the nats tools' credential gets a directory of its own the tools can reach (issue 1952) 2026-10-29 22:00:20 +01:00
jschoubben 2669fc29d8 Re-pin the release sdk; the bus module's tools declare the two removals they hold and leave the credential to the runtime (issue 1952 N1-N3) 2026-10-29 21:54:42 +01:00
jschoubben f7d821b023 nats: the tools run on the process account nats-tools with its own secret, and take the release sdk, so the bus grants them only the four removals (issue 1952 N1-N3) 2026-10-29 21:46:15 +01:00
jschoubben b4e90e5fce Run the bus from its pinned upstream image with the snapshot program and the entrypoint mounted, and write and rehearse the way there and back (issues 1640, 1641, 1642, ADR 0480 clauses 1-3, 5, 6, 11) 2026-10-22 09:55:03 +02:00
jochen 0275c2eeac nats: run 2.11.17, which hands a consumer with several filters every message (hq issue 266) 
On 2.10.29 such a consumer was moved past a message now and then without
handing it over; the controller's events consumer has seven filters, and a
merge on the stream never reached it. The test reproduces the skip on 2.10.29
and keeps the image's release equal to the server it tests.
 2026-10-06 01:29:20 +02:00
jochen f53fc0929b The bus's own tools: server, connections, subscriptions, streams, backlog, buckets, users, user_can 
A Go bundle the runtime launches beside the nats module's server. It reads
the server's monitoring API and the composed user list — never a password
hash — and changes nothing. Reached directly when the endpoint is published,
through the container otherwise: its configuration binds monitoring to the
container's own loopback, so the published port answers nothing today.
 2026-10-04 16:51:33 +02:00