tursodatabase / tursodatabase/libsql
Error: Internal Error: `expected value at line 1 column 1`
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
config:
2024-12-22 15:03:23 libsql-primary-1 | - mode: primary (0.0.0.0:5001)
2024-12-22 15:03:24 libsql-replica-1 | - listening for HTTP requests on: 0.0.0.0:8080
2024-12-22 15:03:23 libsql-primary-1 | - database path: iku.db
2024-12-22 15:03:23 libsql-primary-1 | - extensions path: <disabled>
2024-12-22 15:03:24 libsql-replica-1 | - grpc_tls: no
2024-12-22 15:03:23 libsql-primary-1 | - listening for HTTP requests on: 0.0.0.0:8080
2024-12-22 15:03:23 libsql-primary-1 | - grpc_tls: no
expected value at line 1 column 1
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 reported configuration output and the “expected value at line 1 column 1” error in the libsql primary and replica setup. The payload names no source files or tests, so trace where this configuration or log output is parsed and establish a minimal failing case; done means the reported setup no longer produces the parsing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100