You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test(node): assert the gauges from hand built reports
`ProbeReport` gains `From<Vec<ProviderHealth>>`, so the gauge tests no
longer open sockets and drive another crate's probe just to reach this
crate's publication. They now cover several chains in one report, and
pin the label of the one chain whose key is not its variant name.
Log lines carry the chain's config key rather than its variant name, and
a healthy or uncheckable provider logs at info, so the documented line
per provider appears at the level operators run. Also drops metric
labels from the truncation rationale: no metric carries a fingerprint.
Copy file name to clipboardExpand all lines: docs/foreign-chain-transactions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -562,7 +562,7 @@ Every chain with an inspector is probed, each by the RPC below. `solana` and `et
562
562
563
563
The reported and the configured value are normalized before they are compared, because the same fingerprint has several legal spellings. Starknet's is the chain id felt in lowercase `0x` hex without leading zeros, which providers and operators alike are free to pad and upper-case. The EVM chain id is compared in decimal, the form it is published and configured in, while `eth_chainId` answers a `0x` hex quantity. Bitcoin's genesis hash is compared in lowercase hex, with the leading zeros kept, since they are digits of the hash. Aptos answers its chain id as a number, so only the configured value needs normalizing, and Sui's base58 digest has a single spelling with nothing to normalize.
564
564
565
-
An answer that is no fingerprint at all is reported as the wrong network, carrying the text the provider sent, so the report says what was actually claimed. An answer longer than any real fingerprint is cut short and ends in `_TRUNCATED`, because it is repeated into logs and metric labels.
565
+
An answer that is no fingerprint at all is reported as the wrong network, carrying the text the provider sent, so the report says what was actually claimed. An answer longer than any real fingerprint is cut short and ends in `_TRUNCATED`, because it is repeated into the logs.
566
566
567
567
#### Why drop-and-log on local-config mismatch, not hard-crash
0 commit comments