AndrewSisley
AndrewSisley
> Do we want to keep this ticket open for making our clients eventually behave the same in future? Yes please, and please tweak the description, and link to this...
Please wait until https://github.com/sourcenetwork/defradb/pull/2414 is merged before picking this up, or it will cause annoying conflicts.
This is documented by TestQueryOneToOne_WithVersionOnOuter
wip branch name 1709-version-rel
This is somewhat related to https://github.com/sourcenetwork/defradb/issues/2334 and the current ambiguity as to whether field.ID is global or local (currently there is no location to store unknown fields and I think...
See also https://github.com/sourcenetwork/defradb/issues/1105 and https://github.com/sourcenetwork/defradb/issues/1104 - if this ticket is completed before these two, they should also be closed.
Be careful with this one, is a chance that the test harness is reading after every write and as a result some failures may be test artifacts
> What failures are you talking about? What does reading after writes have to do with this issue? The failures you are seeing in the tests you mentioned in the...
The issue title `An actor granted a write permission still can't write unless also given read permission`, and description body suggest that the current behaviour is unwanted and that you...
> Defra won't overwrite the policy but instead let users who have access to write also have access to read. Without informing/affecting sourcehub? Have you discussed that with @jsimnz and/or...