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.