-
Notifications
You must be signed in to change notification settings - Fork 1
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
Z3 model parsing bug #5
Comments
tchajed
added a commit
that referenced
this issue
Feb 14, 2023
The model parsing code didn't handle auxilliary definitions that aren't part of the signature (there was a comment about this, but we didn't have a test case that exercised it). Now, we don't construct an interpretation for any symbols in the model that aren't in the signature (though their raw form is still available for evaluation). Fixes #5. Signed-off-by: Tej Chajed <tchajed@vmware.com>
Thanks for the report! I fixed this in the branch We can merge that once the |
tchajed
added a commit
that referenced
this issue
Feb 21, 2023
The model parsing code didn't handle auxilliary definitions that aren't part of the signature (there was a comment about this, but we didn't have a test case that exercised it). Now, we don't construct an interpretation for any symbols in the model that aren't in the signature (though their raw form is still available for evaluation). Fixes #5. Signed-off-by: Tej Chajed <tchajed@vmware.com>
tchajed
added a commit
that referenced
this issue
Feb 21, 2023
The model parsing code didn't handle auxilliary definitions that aren't part of the signature (there was a comment about this, but we didn't have a test case that exercised it). Now, we don't construct an interpretation for any symbols in the model that aren't in the signature (though their raw form is still available for evaluation). Fixes #5. Signed-off-by: Tej Chajed <tchajed@vmware.com>
tchajed
added a commit
that referenced
this issue
Feb 21, 2023
The model parsing code didn't handle auxilliary definitions that aren't part of the signature (there was a comment about this, but we didn't have a test case that exercised it). Now, we don't construct an interpretation for any symbols in the model that aren't in the signature (though their raw form is still available for evaluation). Fixes #5. Signed-off-by: Tej Chajed <tchajed@vmware.com>
This was referenced Mar 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Program panics when executing
echo -e "3\nE quorum q\nF node n1 n2 n3\nF value v\n0\n3" | cargo run --release -- infer examples/consensus_epr.fly --solver z3
Error message:
thread 'main' panicked at 'could not find relation k!1058', src/fly/syntax.rs:218:32
Running with
RUST_BACKTRACE=1
yields the following traceThe text was updated successfully, but these errors were encountered: