Recover client from server restarts when handling batons? · tursodatabase/libsql#1856

(2 comments) (0 reactions) (0 assignees)C (16,744 stars) (490 forks)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
Issue 種別: bug
難度: 3
推定時間: 1-3 hours
活動状況: fresh
明確さ: mostly clear
前提条件: Understanding of libSQL client server protocolFamiliarity with baton mechanismKnowledge of error handling in C
初心者向け度: 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.