You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by wy...@apache.org on 2026/09/02 19:35:24 UTC
(maka) branch feat/peer-live-route-recovery updated (658ed0e6fe -> 4e89e78206)
This is an automated email from the ASF dual-hosted git repository.
M4n5ter pushed a change to branch feat/peer-live-route-recovery
in repository https://gitbox.apache.org/repos/asf/maka.git
discard 658ed0e6fe docs(peer): record third review adjudication
discard 5af340583a fix(peer): use canonical connectivity state
discard 3dd3250efc docs(peer): record first review adjudication
discard 444d41c6cb fix(peer): bound live route recovery
discard 080678752b feat(peer): recover live routes in one connection attempt
discard c372473114 refactor(peer): keep one reachability authority
discard d70bcc0f76 fix(peer): bind mesh authority identity
discard 5bbc31d1e1 fix(peer): converge reachability recovery state
discard 6d820721a0 feat(peer): converge Mesh reachability leases
discard 782de09572 fix(peer): keep relay anchor recovery bounded
discard 532ac39a65 feat(peer): recover accepted relay anchors
add 31ad73e87d fix(peer): distinguish borrowed endpoint ownership
add eb0215951a feat(peer): recover accepted relay anchors
add 0b48dcf7ff fix(peer): keep relay anchor recovery bounded
add 408cd5fe50 feat(peer): converge Mesh reachability leases
add c5992fac7c fix(peer): converge reachability recovery state
add c6dcbedf87 fix(peer): bind mesh authority identity
add c6474b493a refactor(peer): keep one reachability authority
add 9277728edf fix(peer): preserve converged mesh exports
add 565654c84d feat(peer): recover live routes in one connection attempt
add 86df86926f fix(peer): bound live route recovery
add a10df77bfb docs(peer): record first review adjudication
add f4f1cb34ed fix(peer): use canonical connectivity state
add 0f426bb460 docs(peer): record third review adjudication
add 4e89e78206 docs(peer): record fourth review adjudication
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (658ed0e6fe)
\
N -- N -- N refs/heads/feat/peer-live-route-recovery (4e89e78206)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../peer-reachability-recovery-plan.md | 2 +
packages/runtime-host/src/peer-mesh/index.ts | 7 +-
packages/runtime-host/src/peer-mesh/owner.ts | 76 +---------------------
.../runtime-host/src/server/execution-service.ts | 25 ++++---
scripts/smoke-release-cli-package.mjs | 65 +++++++++++++-----
5 files changed, 72 insertions(+), 103 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org