avezina-ubik

Since I really don't know how long it's gonna take before PR #1042 will be merged, I made a Dockerfile so we can start using migrate with Turso sooner: ```...

Hey @bryanvaz! Thanks for the review. I updated the README and tried to prioritez the `libsql` scheme since it's the one we mostly see in the Turso docs. My guess...

Hi @keenanwl I will update the README soon with github.com/tursodatabase/libsql-client-go. From what I understand (though I'm a bit confused by Turso's documentation): * `github.com/tursodatabase/libsql-client-go` is used to interact with a...

Hey guys, I noticed that using this driver to interact with a file (e.g. `./migrate -database libsql://file://./my.db -path migrations/ up`) does not work right now. Besides a URL parsing issue...

Oh! I understand your problem now @keenanwl. I assumed you were using the CLI. Since you are already importing `github.com/tursodatabase/go-libsql` from somewhere in your source, you are getting the infamous...

Hi @ainsleyclark Don't think it's gonna happen to be honest. Best bet would be to fork a build and have you own Docker image. I am still using something like...

Hey @hraban, Tried compiling it quickly on my machine and it seems to be working fine. I simply added `SetComplexity` to the decoder and everything compiles and runs smoothly (more...

You are right, it seems to compile anyway since the "new feature" is actually passing through `opus_decoder_ctl` I will submit a PR shortly to add the SetComplexity to the decoder

This should help #54

Hey @hraban , I just checked the build logs and it seems the workflows are using libopus from Ubuntu 24.04, which is version 1.4. This PR depends on a feature...