piker/ai/prompt-io/opencode/20261028T165638Z_b95e7c79_r...

39 lines
1.4 KiB
Markdown
Raw Normal View History

.data: expose websocket reconnect progress at INFO An INFO pikerd still hid websocket connection-success messages. The shared ._util.log emitter is piker.data, but open_feed_bus() configured piker.data.feed. Errors reached bare stderr while INFO diagnostics remained disabled on the actual emitter. Configure the shared logger by its exact log.name and prefer the actor's loglevel over a quieter per-client request for these actor-wide transport diagnostics. Preserve the selected client level passed to provider feed startup. Also, - retain the existing handshake-success report and add URL-tagged readiness after fixture setup and first-message relay once per connection, including replacement sockets. - include the URL in receive-timeout reset errors so Binance's independent bookTicker and aggTrade routes are distinguishable. - prove real console INFO visibility through production feed startup, stopping before provider lookup, then restore logging state; the original code fails with the emitter at WARNING. - extend the loopback recovery test to verify both readiness reports and the first relay from the replacement connection. First-message relay is raw websocket traffic, not proof that parsed market data or chart updates have recovered. The 18 logging/Binance/websocket cases pass; live reporting qualification remains separate. This is a local follow-up, not a downstream cherry-pick. The 54da2973 websocket cleanup and 5adf77a9 namespace fix do not configure this shared emitter. Relevant local histories and dirty IB-history/TIPC deltas contain no equivalent wiring fix. Prompt-IO: ai/prompt-io/opencode/20261028T165638Z_b95e7c79_reconnect_logging.md (this patch was generated in some part by `opencode` using `gpt-6.1-sol` (`openai`))
2026-10-28 17:13:26 +00:00
---
created_at: 2026-10-28T16:56:38Z
generated_by:
harness: opencode
provider: openai
model: openai/gpt-6.1-sol
git_ref: b95e7c79
diff_cmd: git diff HEAD~1..HEAD
---
Confirmed the existing INFO handshake-success log was hidden by
logger wiring: websocket code emits on piker.data, while feed
startup configured piker.data.feed. The baseline regression leaves
the emitter at WARNING for an INFO daemon and ERROR client.
> `git diff HEAD~1..HEAD -- piker/data/feed.py`
Configure the actual shared ._util.log namespace, with daemon
verbosity taking priority over client verbosity for actor-wide
transport diagnostics.
> `git diff HEAD~1..HEAD -- piker/data/_web_bs.py`
Keep the existing handshake-success message. Add INFO readiness
after fixture setup and first-message relay once per connection.
Include the URL in the receive-timeout reset diagnostic.
> `git diff HEAD~1..HEAD -- tests/test_logging.py tests/test_websocket.py`
Prove production startup enables real console INFO on the websocket
emitter without contacting a provider. Extend the real loopback
recovery test to require readiness for both connections and one
first-message report for the connection delivering fresh data.
All 18 targeted logging/Binance/websocket cases passed. No live
provider/daemon operations were performed by the agent. First relay
is raw websocket traffic; parsed market-data recovery remains a
separate live observation.