-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The stream has expired due to inactivity #3
Comments
Here's a reproduction https://github.com/thetutlage/knex-turso-example |
Just as an aside, I had better luck connecting with |
how your connection got established |
I have this problem too. I tried playing with the pool config but didn't work. The config looks like this: knex({
client: Client_Libsql,
connection: { filename: "<URL>" },
pool: { min: 0, idleTimeoutMillis: 1000, reapIntervalMillis: 100 },
}) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to the issues reported in Python lib tursodatabase/libsql-experimental-python#41 and Go lib tursodatabase/libsql#985
I am also getting the same error when using LibSQL with Knex. I see this PR that resets the connection when resource is released to the pool for the Go implementation tursodatabase/libsql#1100. Do we have to do something similar?
The text was updated successfully, but these errors were encountered: