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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
The spot WS consumer now authenticates to xenon's realtime relay. xenon v0.9.0 rejects a WebSocket upgrade from a service client unless it carries X-API-Key and no Origin header. XenonWsClient (the live session and the fallback probe) now sends X-API-Key: $XENON_QUERY_API_KEY on the upgrade when the key is set, and never an Origin. Older relays ignore the header. websockets logs every upgrade header and frame at DEBUG, so the client hands it a logger that renders each record (message, args, exception, stack) to text and prints the key as ***; the consumer's own failover and probe logs name only the exception type and, for a rejected upgrade, its HTTP status, because a rejection response can echo the key. Without the key, xenon v0.9.0 answers 401 and the consumer fails over to massive, so the mini's argon .env must carry XENON_QUERY_API_KEY (the same key the REST greeks API needs) and the WS consumer must restart to pick up a rotated key.