tursodatabase / tursodatabase/libsql-js
Sync example fails with latest libSQL
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
With https://github.com/libsql/libsql-js/pull/54, the sync example fails as follows:
penberg@vonneumann sync % node example.js
2023-11-01T09:20:21.706640Z INFO libsql_replication::replicator: Attempting to perform handshake with primary.
2023-11-01T09:20:21.706790Z INFO libsql::replication::remote_client: Attempting to perform handshake with primary.
2023-11-01T09:20:21.972033Z ERROR libsql_replication::replicator: error connecting to primary. retrying. error: Replicator client error: invalid length: expected length 32 for simple format, found 0
Contributor guide
No contributing guide indexed for this repository
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 running the sync example with node example.js and inspect the example referenced by the issue alongside pull request #54. Trace the handshake failure shown in the log and verify that the sync example connects successfully with the latest libSQL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, sqlite
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100