You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good catch. I agree that leaking timestamps into version numbers is quite unfortunate, and we should strive to remove them. We might also consider doing the same in the original what4 code that this was based on, although the what4 code isn't used for caching purposes (just debugging information), so it's less important there.
Also, I agree that it would be better to run abc -q "version;quit" rather than abc s -q "version;quit", as the latter has the unfortunate side effect of starting an interactive abc session. Most of the time, we are invoking abc subprocesses in a non-interactive way, so we usually don't notice this. It is definitely noticeable when you try to run the same command in an interactive shell, however (given that you have to Ctrl-D afterwards to exit).
Determining the solver version for
SBV.ABC
currently yields a string specific to the operating system.For example, this is from Ubuntu:
And here's the output on macOS:
They're the same version, yet they'll unfortunately produce different hash keys.
A possible solution might be to match the version string inside those messages and use that as input to the hash key instead?
Also, it seems that the arguments
["-q", "version;quit"]
would be correct, without the leading"s"
?The text was updated successfully, but these errors were encountered: