tursodatabase/libsql

Recover client from server restarts when handling batons?

Open

#1,856 建立於 2024年11月29日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)C (16,744 star) (490 fork)batch import
enhancementhelp wantedquestionremote protocol

描述

Currently, I think that when a client holds a server-issued baton and attempts to send it back after a server restart, the request fails with a BatonInvalid error. This error breaks the client's workflow and requires manual intervention.

If this turns out to be the case, let's fix that so thatif a BatonInvalid error occurs and no transaction is in progress, the client should:

  • Automatically restart the stream
  • Obtain a new baton from the server
  • Continue normal operation

貢獻者指南

技術棧
csql
領域
backenddatabase
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of libSQL client server protocolFamiliarity with baton mechanismKnowledge of error handling in C
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the current handling of BatonInvalid errors in the client code. Examine the client's error recovery logic, particularly in the context of server restarts. Look into the libSQL client source code, likely in the client library files, to identify where batons are sent and how errors are propagated. Consider implementing automatic stream restart and baton re acquisition upon BatonInvalid when no transaction is active.