The ``retrying`` publication landed only on the supervisor-rebuild path (WS thread dies). On the live link ``_auto_reconnect`` is on, so a receive-loop error runs lark-oapi's ``_reconnect()`` ladder *inside* the receive loop — the thread never dies and ``gateway_state.json`` kept saying ``connected`` while the link was down. Set the SDK's ``Client.on_reconnecting`` observer (lark-oapi 1.6.8 ws/client.py, fired first thing in ``_reconnect()``) from ``_apply_runtime_ws_overrides``; it hops to the adapter loop and publishes ``retrying`` through the same runtime-status call the supervisor uses, gated on the client still being the live one. ``connected`` is re-stamped by the existing ``_ws_link_up`` hook once the ladder's ``_connect()`` schedules a new receive loop, so no ``on_reconnected`` hook is needed. Docs: the WebSocket-mode section now says a dead link is rebuilt by Hermes' supervisor and shows ``retrying`` in gateway status until re-established. Test: test_sdk_reconnect_ladder_publishes_retrying (red before: FeishuAdapter has no _ws_link_retrying / observer never set; green after).
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.