jcasbin/redis-adapter

Redis adapter for Casbin

redis-adapter's Issues

Caused by: java.lang.NoClassDefFoundError: org/apache/commons/collections/CollectionUtils

Caused by: java.lang.NoClassDefFoundError: org/apache/commons/collections/CollectionUtils
at org.casbin.adapter.RedisAdapter.addPolicy(RedisAdapter.java:80)
at org.casbin.jcasbin.main.InternalEnforcer.addPolicy(InternalEnforcer.java:49)
at org.casbin.jcasbin.main.ManagementEnforcer.addNamedPolicy(ManagementEnforcer.java:327)
at org.casbin.jcasbin.main.ManagementEnforcer.addPolicy(ManagementEnforcer.java:267)
at org.casbin.jcasbin.main.Enforcer.addPermissionForUser(Enforcer.java:268)

Create the Redis adapter for jCasbin

i want public boolean addPolicies(List<List<String>> rules), please

public boolean addPolicies(List<List> rules)

Add CI badge to README

https://github.com/jcasbin/redis-adapter#redis-adapter

Add the semantic-release.

the performance can be further improved for addPolicies()

    > @xudaren already here:

redis-adapter/src/main/java/org/casbin/adapter/RedisAdapter.java

Lines 109 to 116 in 686bc3e

	/**
	* AddPolicies adds policy rules to the storage.
	*/
	public void addPolicies(String sec, String ptype, List<List<String>> rules) {
	for (List<String> rule:rules) {
	addPolicy(sec, ptype, rule);
	}
	}

the performance can be further improved

Originally posted by @xudaren in #14 (comment)

Otherwise, there are too many network interactions

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Deployment to maven failed.

The deployment to maven failed for an unknown reason.

Please check the logs on the CI server to see what happened.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Deployment to maven failed.

The deployment to maven failed for an unknown reason.

Please check the logs on the CI server to see what happened.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Implement the function named "removefilteredpolicy".