tlyyxjz commented on issue #917: URL: https://github.com/apache/casbin/issues/917#issuecomment-5469257617
Really nice minimal repro. The `!some(where(p.eft == deny))` clause makes any unrelated deny row poison the entire evaluation — easy to forget when you mix ABAC (subject attributes) with policy effects. That ABAC × deny interaction is a classic "silently wrong" trap: it looks fine in tests, fails deep in prod. Exactly the kind of matcher/effect combination an automated diagnostic (over policy_effect + matcher) should catch before it ships. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
