Jonathan Whitaker

Why have the `RequestTimeout` config if the context dominates, especially if `context.Background()` overrides the top-level config setting? Perhaps I may suggest that `RequestTimeout` is just dropped altogether in favor of...

> That's a good suggestion but unfortunately if we make that change now, the change will be backwards incompatible. @anudeeb looking forward to `github.com/aws/aws-dax-go/v2` 😄 !

I've started a pull-request to introduce this feature (see https://github.com/prusa3d/PrusaSlicer/pull/11903 for progress updates). I will be working on it over the upcoming holiday. It will probably take me longer than...

@DanCech I changed the base branch this PR is targeting because we're devising a strategy for how to handle community storage contributions without taking on the burden of the storage...

@KlausVii if you have some sample tuples to share that would be great. That being said, in the meantime, the problem here stems from bi-directional relationships between user and tenant....

@ilaleksin What is the standard around the go-grpc-middleware for this deprecation? What are other people doing? Do you have some examples you can share from other Go projects so that...

Supersedes #1590

> This is one test case I'm still pondering though, could see it going either way: > > ``` > { > name: "chained_negation_14", > tuples: []*openfgav1.TupleKey{ > tuple.NewTupleKey("document:1", "viewer",...

Regarding the changes to the API in https://github.com/openfga/api/pull/157. This line https://github.com/openfga/api/pull/157/files#diff-d3a74ea9ecaac0a46611253dc0c4bc9c402e2ad9eb255cd41d07266453e258f0R1564 we should avoid duplicating that stuttered field definition. Since this is a new addition to the API, let's follow...

This PR is titled "Support Context in Assertions API" but we're not adding Context to to the Assertions API. There is no corresponding PR in openfga/api that adds `context` field...