Replace link CA… in the Relays page header starts a replacement of the link CA every relay shares. It goes as replaceLinkCa: "start" on one relay, sent alone. It only shows when the server sends linkCaReplacing (RL-34 or later) and a relay has joined.
While one is under way, a line above the relays gives the start time and names the relays it waits for. It has Finish now…, which is marked destructive when relays would be left behind, and Cancel it…. The page refetches every 15 seconds, because the server finishes the replacement by itself.
On a relay's card: linkCaWaiting when it doesn't trust the new CA yet, and linkCaOld (start a new join) when it only trusts a replaced CA. The latter replaces every other note, since such a relay can't link.
Checks: typecheck, lint, i18n + i18n:check (19 strings), npm test (975, with new model tests), build, notice-check, and prettier on the touched files.
Not previewed in the browser: the states need a joined relay in the middle of a replacement. The server's relay_link_tests covers that flow end to end.
The console part of RL-34 (server: inbuxa/inbuxa-server#273).
- **Replace link CA…** in the Relays page header starts a replacement of the link CA every relay shares. It goes as `replaceLinkCa: "start"` on one relay, sent alone. It only shows when the server sends `linkCaReplacing` (RL-34 or later) and a relay has joined.
- **While one is under way**, a line above the relays gives the start time and names the relays it waits for. It has **Finish now…**, which is marked destructive when relays would be left behind, and **Cancel it…**. The page refetches every 15 seconds, because the server finishes the replacement by itself.
- **On a relay's card**: `linkCaWaiting` when it doesn't trust the new CA yet, and `linkCaOld` (start a new join) when it only trusts a replaced CA. The latter replaces every other note, since such a relay can't link.
Checks: typecheck, lint, i18n + i18n:check (19 strings), `npm test` (975, with new model tests), build, notice-check, and prettier on the touched files.
Not previewed in the browser: the states need a joined relay in the middle of a replacement. The server's `relay_link_tests` covers that flow end to end.
Replace link CA… on the Relays page starts a replacement of the link CA
every relay shares, sent as replaceLinkCa on one relay. While it's under
way a line above the relays says since when and which relays it waits
for, with Finish now… and Cancel it…, and the page looks again every 15
seconds, as the server finishes it by itself. A relay that doesn't trust
the new CA yet says so on its card; one that only trusts a replaced CA
asks for a new join, and nothing else.
The action shows only for a server that sends linkCaReplacing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The console part of RL-34 (server: inbuxa/inbuxa-server#273).
replaceLinkCa: "start"on one relay, sent alone. It only shows when the server sendslinkCaReplacing(RL-34 or later) and a relay has joined.linkCaWaitingwhen it doesn't trust the new CA yet, andlinkCaOld(start a new join) when it only trusts a replaced CA. The latter replaces every other note, since such a relay can't link.Checks: typecheck, lint, i18n + i18n:check (19 strings),
npm test(975, with new model tests), build, notice-check, and prettier on the touched files.Not previewed in the browser: the states need a joined relay in the middle of a replacement. The server's
relay_link_testscovers that flow end to end.