tursodatabase / tursodatabase/libsql
hrana3-protobuf no longer supported in Turso?
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Hey team, it's been a while since I've used Turso but in the past the /v3-protobuf endpoints would allow us to use protobuf messages for everything. They seem to still be alive in dockerized libsql but not in hosted Turso. Is this the case?
$ curl -H 'Authorization: Bearer <TOKEN>' https://celest-auth-test-dillon-celest.aws-us-west-2.turso.io/v3
{"msg":"Hello, this is HTTP API v3 (Hrana over HTTP)"}
$ curl -H 'Authorization: Bearer <TOKEN>' https://celest-auth-test-dillon-celest.aws-us-west-2.turso.io/v3-protobuf
{"error":"route not found: [\"v3-protobuf\"]"}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two curl requests against the hosted Turso endpoint and compare the result with dockerized libSQL, where the issue says /v3-protobuf remains available. Trace the hosted HTTP API route handling and determine whether the missing endpoint is intentional or a regression; done means documenting the support status or identifying the needed fix.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100