Investigate session expiry pause behavior (errcode -14)

[Oaklight]

Background

The official SDK pauses for 1 hour when receiving errcode -14 (session expired). Our current implementation raises SessionExpiredError and the dispatcher stops immediately.

Current behavior

• _protocol.py: errcode == -14 → raises SessionExpiredError
• client.py _poll_loop: catches SessionExpiredError → break (dispatcher stops)
• User must manually re-login

Questions to investigate

1. Does the session auto-recover after the 1-hour pause, or is re-login always required?
2. Is the 1-hour pause a server-imposed cooldown (will immediate re-login fail)?
3. How frequently does session expiry occur in normal usage?
4. Does the server return any additional fields with errcode -14 (retry hints, TTL)?

Phase 1 (logging)

• Enhanced logging on SessionExpiredError: full error details, timestamp
• Log complete response body when errcode == -14

Phase 2 (implementation, based on findings)

• If auto-recovery: sleep + retry with configurable duration
• If re-login required: keep break + provide callback/event hook
• Consider exposing a on_session_expired event

Files

• src/weilink/_protocol.py
• src/weilink/client.py

[Oaklight]

Phase 1 (logging) done in 2671ddd:

• _recv_session_locked() in client.py now logs session name, errcode, and errmsg at WARNING level when SessionExpiredError is caught (before clearing cursor/context tokens)
• _protocol.py already logs the full response at WARNING level when errcode == -14
• Keeping issue open for Phase 2 — will implement retry/callback based on what the logs reveal about server behavior