tursodatabase / tursodatabase/libsql
Import of @libsql/client hangs under very specific circumstances
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
If @libsql/client is imported in nodejs under very specific circumstances (pino + anthropic is imported before + vscode debugger is attached!)
Then the program just hangs indefinitely on the import. I have reduced this to a minimal example in order to reproduce it.
Here's the full reproduction: https://github.com/phiresky/wat-repro
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 with the minimal reproduction at https://github.com/phiresky/wat-repro and run it under Node.js with pino and anthropic imported before @libsql/client while the VS Code debugger is attached. Trace the import hang and verify that the reproduction no longer hangs indefinitely under those stated conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, sqlite, vscode
- Domain
- backend, databases, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100