Open MarceColl opened 3 months ago
Actually just after submitting I realized that npm exec quint -v
gives the same version as npm -v
, so it seems that it consumes npm exec
consumes arguments in a weird way.
By running it as npm exec quint verify bank.qnt -- --invariant=no_negatives
it does correctly find a violation as expected.
I'm leaving the issue open in case you wanna add something in the docs about this for people that run it from inside a project.
Ah, great that you found the issue! The npm exec quint -v
result was the first thing I spotted, since we are currently at 0.21.1
.
I'll add a :bulb: warning in the getting started guide with the proper command for people running it with a local installation. I've used that many times before, but always with npx
, so it doesn't have this problem:
npx quint verify bank.qnt --invariant=no_negatives
Thanks for the detailed reporting!
I'll just change the title of this issue so it matches your new request.
Hi!
From lobste.rs I was told to post here, hopefully I haven't made a very dumb mistake.
I followed the Getting Started tutorial and I never got the expected violation both with the simulator and with the validator.
Steps I followed:
Installed the package in a local folder (I cannot install globally)
Created a new file bank.qnt with the following value
Then I ran the command as specified in the tutorial, but prefixed with
npm exec
I thought maybe the simulator didn't test negative values, but the states clearly contain them. Just in case I tried verify
Some info