-
Notifications
You must be signed in to change notification settings - Fork 5
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
Translate.tla
counterexample using modelator tla tla-trace-to-json-trace <filename>
results in parsing error.
#56
Comments
.tla
counterexample/trace using ./modelator tla tla-trace-to-json-trace <filename>
results in parsing error for particular file..tla
counterexample using modelator tla tla-trace-to-json-trace <filename>
results in parsing error.
The current nom parser doesn't handle nested functions. It will parse following successfully,
but not this
also not this
@danwt, it fails on the above |
Sorry for the weekend work. I just had to finish the nested parser. Anyway, this does not resolve the issue. Now it complains, it didn't parse the whole
Looks like the states in modelator/modelator/src/artifact/tla_trace.rs Lines 26 to 30 in b45faeb
|
After a quick look, it seems,
Removing those from |
@danwt I pushed a new TLA file parser. This should fix this issue :) |
Looks like, the mentioned TLA file is not a proper TLA file. It should be the trace generated from We have two choices.
|
I went with option (2). TLA trace from |
Co-authored-by: Daniel Tisdall <[email protected]>
Bug:
Running
./modelator tla tla-trace-to-json-trace examples/counterexample1.tla
does not work. Results in parsing error.Content of
counterexample.tla
is at the bottom of this issue.Expected:
JSON output for translated tla.
Log:
Additional info:
Tested on release in (06ed539eb) latest
.tla file in question:
The text was updated successfully, but these errors were encountered: