-
Notifications
You must be signed in to change notification settings - Fork 38
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
v0.32.0 can no longer be used as an axum state (!Sync
)
#52
Comments
This blocked my getting started experience with Turso entirely alas. |
Same here |
Failed to build for 0.33. Had to revert back to 0.31. I wonder what was the underlying change introduced causing this. |
Hi all, sorry about the delay. We have actually been working on a new libsql client that lives in https://github.com/tursodatabase/libsql we are almost ready to publish it to cratesio which we can do next week. This client explicitly supports working in axum because it implements both libsql = { git = "https://github.com/tursodatabase/libsql" } if you just want to compile the the http only features (not do any C building to build the sqlite3 code) you can do that like so: libsql = { git = "https://github.com/tursodatabase/libsql", default-features = false, features = ["remote"] } This example shows you how you can connect either via the http/remote protocol or open a normal in memory libsql-sqlite3 database. Feel free to ping me on discord if you run into any issues! |
The following minimal Axum code used to work with v0.31.0, but no longer works with the last version. I believe this is because the local client is no longer
Sync
in v0.32.0 (while it was in v0.31.0).Error
With v0.32.0 the following snippet of the compile error is interesting:
The text was updated successfully, but these errors were encountered: