Christopher Chianelli

> I imagine it is the same SolverConfig if I just to change the number of number of customers, their locations - and demands for each location will be different...

Sadly, exception info is lost when setting a Python exception as the cause for a Java exception. Where is `request` defined (it is not a parameter for `solve`)? `solve` look...

Looking at the error, I think it is caused because `AvailabilityType` is an `Enum`. I recall enums working previously; what is your Python version (this is relevant, since we translate...

At this point, I am almost certain this is a pytest bug, since this code still cause the internal error: ```python def test_reproducer(): try: code_that_cause_exception() except: raise Exception ```

Forgot that `raise Exception` is a short for `raise Exception from last_raise_exception`. Managed to get a minimal reproducer; it has to do with generated classes; Reproducer is https://github.com/Christopher-Chianelli/issue-reproducer/tree/jpype-1178

If the generated class has source information (i.e. `classWriter.visitSource("MyFile.py", "debug");` and `methodVisitor.visitLineNumber(0, line);`), then the exception does not occur.

I think you checked out the wrong branch; the branch should be `jpype-1178` not `drools-classloader-reproducer` (which is the default branch)

This is odd, - Tried `pytest` without `mvn clean install`, got the above result on both this and #1180 (i.e. what is expected if the issue was fixed) - Did...

If the `@PlanningVariable` and `@PlanningListVariable` are defined on the same class, there is a better error message: ``` java.lang.UnsupportedOperationException: Combining basic variables ([Line.product variable]) with list variables (Line.jobs variable) on...

I am pretty sure there are no tests for `@PlanningVariable` + `@PlanningListVariable` on different entities, so if it supported, it not tested. Additionally, that exception is from the default phase...