-
Notifications
You must be signed in to change notification settings - Fork 368
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
Building v0.47.0 fails - cannot use generic type ristretto.Cache[K z.Key, V any] without instantiation #825
Comments
It looks like |
Yeah this compatibility was broken here: dgraph-io/badger@8e08c43 without a v5 bump, I'd suggest downgrading to 4.2.x until the fix this breaking change. The change doesn't need to happen at ristretto, but needs to occur at the implementation end. As ristretto is v0 the guarantee doesn't effectively exist, but the implementer needs (badger) to bump in this instance since the bump to this untagged version causes the breakage. |
Upgrade Go please |
I'm running
Agreed, this is an unfortunate combination of factors. Will discuss in this issue in the ristretto repo 👍 |
The API of ristretto changed from 0.1.1 -> 1.0.0. github.com/ory/[email protected] seems to have bumped ristretto |
I am unsure why the issue has been closed, as it remains unresolved 😢 :
|
Because of the incompatibility, ristretto 1.0.0 has been retracted:
|
I mean you're upgrading ory/x ? Just don't upgrade it? The warning is just a warning, it doesn't break the build. You can ignore it. The warning just is there because they messed up the versioning. |
Preflight checklist
Ory Network Project
No response
Describe the bug
I'm building a local OIDC provider and using BadgerDB as my storage for users and registered applications.
After adding BadgerDB
v4.3.0
, thego build
command fails with output suggestingristretto.Config
is not instantiated corrected.Reproducing the bug
Create a go.mod with these dependencies:
Create a
main.go
that instantiates BadgerDB and ory/fosite:Click to expand...
Run
go build
Relevant log output
The text was updated successfully, but these errors were encountered: