Fennecs
Results
2
comments of
Fennecs
Sure, yes looks like the issue is actually bumping ash postgres from 2.6.8 to 2.6.15 or 2.6.16 actually and not ash - ash can be bumped fine. I think theres...
Seems like adding `require_atomic? false` in corresponding locations where `update` is called that triggers the authorisation fixed it in our tests -- So possible more like a bad error message?