satisfies test fails if assertion is not provided

[poolis]

Describe the bug
satisfies test fails if assertion is not provided despite there being a default value for the argument.

I believe the reference satisfies$default$2 should be satisfies$default$3 but I need to test that.

To Reproduce

from pydeequ.checks import *
from pydeequ.verification import *

check = Check(spark, CheckLevel.Warning, "test satisfies")

checkResult = VerificationSuite(spark)
.onData(df)
.addCheck(
check
.satisfies("r in ('123','456','789')","r cannot contain any values excpet"))
.run()

Error:

py4j.Py4JException: Method satisfies$default$2([]) does not exist

--> 542 else getattr(self._Check, "satisfies$default$2")()
543 hint = self._jvm.scala.Option.apply(hint)
544 self._Check = self._Check.satisfies(columnCondition, constraintName, assertion_func, hint)

Expected behavior
Test runs without error

Additional context
Spark 3.3, pydeequ==1.1.1

[poolis]

I have verified that satisfies$default$3 resolves the issue, I will submit a PR.

[github-actions]

You're correct. Looking at the code in checks.py, the satisfies method uses getattr(self._Check, "satisfies$default$2")() but since the Scala method signature is satisfies(columnCondition, constraintName, assertion, hint, ...), the assertion is the 3rd parameter, so the default accessor should be satisfies$default$3.

This is indeed a bug. Thanks for verifying the fix — feel free to submit your PR and we'll get it merged.

---

Generated by AI (model: us.anthropic.claude-opus-4-6-v1, prompt: cf3780e5) — may not be fully accurate. Reply if this doesn't help.

[nikolauspschuetz]

This looks resolved on current master. Check.satisfies now defaults the assertion via satisfies$default$3 when none is supplied (pydeequ/checks.py:558-562), rather than the satisfies$default$2 reference in the traceback. The no-assertion path is also covered by a test — tests/test_checks.py:894 calls self.satisfies("b >=2", "b greater than or equal to 2") with no assertion argument and passes. I believe this can be closed.

[github-actions]

You're correct — this issue has been resolved on the current master branch. The satisfies method in checks.py now correctly references satisfies$default$3 for the assertion parameter default, and there's test coverage confirming the no-assertion path works. This can be closed.

---

Generated by AI (model: us.anthropic.claude-opus-4-6-v1, prompt: 67928783) — may not be fully accurate. Reply if this doesn't help.