Super administrator's authority is invalid when using priority matching

[shink]

problem

When using the following configuration, two error occurs.

1. Super administrator's authority is invalid when using priority matching
2. When using an adapter such as jdbcAdapter, the first time the result was wrong, but everything is correct after that

model

[request_definition]
r = sub, obj, act

[policy_definition]
p = priority, sub, obj, act, eft

[role_definition]
g = _, _

[policy_effect]
e = priority(p.eft) || deny

[matchers]
m = g(r.sub, p.sub) && r.obj == p.obj && r.act == p.act || r.sub == 'root'

policy

p, 10, data1_deny_group, data1, read, deny
p, 10, data1_deny_group, data1, write, deny
p, 10, data2_allow_group, data2, read, allow
p, 10, data2_allow_group, data2, write, allow

p, 1, alice, data1, write, allow
p, 1, alice, data1, read, allow
p, 1, bob, data2, read, deny

g, bob, data2_allow_group
g, alice, data1_deny_group
g, tony, data1_deny_group

request

alice, data1, write    // Expected: true, Actual: true
bob, data2, read    // Expected: false, Actual: false

root, data1, write    // Expected: true, Actual: false
root, data2, read    // Expected: true, Actual: false
root, data1, read    // Expected: true, Actual: false

All user root requests should be allowed.

[shink]

@mango-6bd Please confirm whether the above is consistent with what you have described.

[mango-6bd]

Yes,consistent

[Dzy-yubai]

Why did I test correctly in the latest version of JCasbin

[shink]

@Dzy-yubai I will confirm again.

[hsluoyz]

@shink yeah, if there's no issue actually, we will close here.

[shink]

@Dzy-yubai Thank you for your reminder.

@mango-6bd I tested it with the latest version of jcasbin(1.10.0), but this error did not appear. Please use the latest version of jcasbin to confirm.