-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@optapy.problem_fact => java.lang.VerifyError: Bad type on operand stack #146
Comments
While debugging I ran an untouched version of the Employee Scheduling quickstart. Despite making no changes, it crashes as well. However, I can run the school timetabling quickstart without error. Here is the debug logs of Employee Scheduling quickstart:
|
removing the |
Looking at the error, I think it is caused because |
Pyhon 3.9.0 |
I now have it working fine on Python 3.11.1 |
I'm modifying the Employee Scheduling quickstart, however I'm running into an error with the @problem_fact decorator.
Some context: my goal is to create a pilot rostering tool for already scheduled flights. The complexity comes in that I have a
Pilot
problem_fact
Class andDuty
planning_entity
Class. Pilots get assigned to duties, but I also want to keep track of the duties assigned to a pilot to ensure they aren't flying too many hours per day, among other constraints. The Pilot class therefore hasget/set_duties
planning_list_variable
functions. This causes a circular reference problem. The classes rely on each other being instantiated first before they can reference them in their own instantiation. I solved this by taking those function definitions out of the class and assigning them after all classes have been instantiated. I suspect this might be causing the problem in some way.Anyways,
@optapy.problem_fact
is throwingjava.lang.VerifyError: Bad type on operand stack
when aproblem_fact
class that referencesPilot
is instantiated.See my stackoverflow question for more details.
Any assistance would be much appreciated.
The text was updated successfully, but these errors were encountered: