From d8d73d5e16ccdd4a1339786cf870ed1754c6ea5f Mon Sep 17 00:00:00 2001 From: feruzm Date: Wed, 5 Aug 2026 07:46:06 +0000 Subject: [PATCH] chore: update renamed repo references (vision-web, vision-mobile) --- .github/workflows/main.yml | 4 ++-- CLAUDE.md | 2 +- README.md | 2 +- dotnet/README.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index b5cf252c..1ae38f83 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -90,8 +90,8 @@ jobs: # Roll the freshly-pushed image out to the running `vision_vapi` swarm service in each # region, so a vision-api change (e.g. rotating Feature Spotlight content) ships on its - # own instead of waiting for the next vision-next deploy. Mirrors the converge-wait that - # vision-next uses for `vision_web`. Assumes the swarm service is named `vision_vapi` + # own instead of waiting for the next vision-web deploy. Mirrors the converge-wait that + # vision-web uses for `vision_web`. Assumes the swarm service is named `vision_vapi` # (stack `vision`, service `vapi`) — verify once with `docker service ls`. deploy: needs: build diff --git a/CLAUDE.md b/CLAUDE.md index 8a7c69c1..271d1b2f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -68,7 +68,7 @@ Handlers are `public static async Task Name(HttpContext ctx)` methods on static ## Upstream node failover -`NodeHealthTracker` (adopted from the vision-next SDK) holds per-node health state: 429 responses park a node for `Retry-After` (or an escalating window), recent failures deprioritize it, and a latency EWMA orders the pool best-first with config order as tiebreak. Two clients build on it: +`NodeHealthTracker` (adopted from the vision-web SDK) holds per-node health state: 429 responses park a node for `Retry-After` (or an escalating window), recent failures deprioritize it, and a latency EWMA orders the pool best-first with config order as tiebreak. Two clients build on it: - `HiveRpcClient` (Hive JSON-RPC): RPC-level errors (JSON `error` field) surface immediately without failover — they're application errors, not node health. The typed helpers additionally validate the result *shape* (`get_accounts` → array, `get_dynamic_global_properties` → object): a 200 with valid JSON but no usable result is a node failure that fails over — without this, a node serving malformed 200s is recorded as healthy and stays ranked first (observed in production as multi-hour windows of token-validation 401s). - `EngineRpcClient` (Hive-Engine): one instance per pool — the `/contracts` RPC pool and the history-API pool. The portfolio `Find` calls are fixed-shape queries that always yield a `result` array on a healthy node, so an error payload or non-JSON body *is* a node failure and rolls over to the next node. The raw passthroughs (`engine-api`, `engine-account-history`) fail over only on transport errors and 429/5xx; other responses belong to the caller's query and pipe as-is. diff --git a/README.md b/README.md index d8e84e5b..b891cbdf 100644 --- a/README.md +++ b/README.md @@ -96,4 +96,4 @@ results, and how to regenerate the crypto golden vectors. To report a non-critical issue, please file an issue on this GitHub project. [//]: # 'LINKS' -[ecency_vision]: https://github.com/ecency/vision-next +[ecency_vision]: https://github.com/ecency/vision-web diff --git a/dotnet/README.md b/dotnet/README.md index dafe9444..c61b44be 100644 --- a/dotnet/README.md +++ b/dotnet/README.md @@ -47,7 +47,7 @@ dotnet/ `HiveRpcClient` keeps the dhive `Client` parameters the Node service used (`timeout: 2000`, `failoverThreshold: 2`) but replaces dhive's simple ring -failover with a health tracker adopted from the vision-next SDK's +failover with a health tracker adopted from the vision-web SDK's `NodeHealthTracker` (simplified for a proxy's call rates): - **Per-node health state**: consecutive failures, rate-limit parking, and a