Skip to content
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

2.8.2: Gecode::FlatZinc::AST::TypeError #768

Closed
informarte opened this issue Dec 15, 2023 · 3 comments
Closed

2.8.2: Gecode::FlatZinc::AST::TypeError #768

informarte opened this issue Dec 15, 2023 · 3 comments
Labels
bug resolved Issue is resolved and the feature or fix will be part of next release

Comments

@informarte
Copy link

rotating-workforce-scheduling:

> minizinc rotating-workforce-scheduling.mzn rws-instance-e-25-s-7.dzn
terminate called after throwing an instance of 'Gecode::FlatZinc::AST::TypeError'
=====ERROR=====

opt-cryptanalysis:

> minizinc mznc2017_aes_opt.mzn r1.dzn 
terminate called after throwing an instance of 'Gecode::FlatZinc::AST::TypeError'
=====ERROR=====
@Dekker1
Copy link
Member

Dekker1 commented Dec 18, 2023

This seems like it would be a problem in the Gecode code base. We will further diagnose and fix the problem where appropriate

@Dekker1 Dekker1 added the bug label Dec 18, 2023
@cyderize cyderize added the resolved Issue is resolved and the feature or fix will be part of next release label Jan 25, 2024
@informarte
Copy link
Author

@guidotack, @cyderize, I tested build1150712751 and found that the issue with opt-cryptanalysis is resolved. However, the issue with rotating-workforce-scheduling has not yet been resolved. MiniZinc 2.7.6 produces this solve goal:

solve :: seq_search([bool_search(X_INTRODUCED_717_,input_order,indomain_max,complete), ...

while MiniZinc 2.8.2 produces:

solve :: seq_search([bool_search([int_eq(X_INTRODUCED_101_,4),int_eq(X_INTRODUCED_108_,4), ...

@cyderize cyderize removed the resolved Issue is resolved and the feature or fix will be part of next release label Jan 28, 2024
guidotack pushed a commit that referenced this issue Jan 28, 2024
@cyderize cyderize added the resolved Issue is resolved and the feature or fix will be part of next release label Jan 28, 2024
@cyderize
Copy link
Member

Thanks @informarte - these turned out to be two separate bugs - hopefully they're both fixed now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug resolved Issue is resolved and the feature or fix will be part of next release
Projects
None yet
Development

No branches or pull requests

3 participants