SparQ execution error with Debian Testing, kernel 5.19.0, g++ 12.2.0, and SBCL 2.2.3

[johanmazelanssi]

My configuration is the following: Debian Testing with kernel 5.19.0, g++ 12.2.0, and SBCL 2.2.3. I use the SparQ version from the master branch from this repository.

I am trying to use constraint reasoning and quantify.

• Constraint reasoning (works after some file trickery) The command I want to execute is: sparq constraint-reasoning allen check-consistency "((i0 b i2) (i0 o i1) (i1 o i2))". I get this error message: ; processing (SHADOWING-IMPORT (QUOTE #)) ; processing (DEF-TOOL ("translate" # ...) ...) ; processing (DEF-TOOL ("translate" # ...) ...) ; processing (DEF-TOOL ("translate" # ...) ...) ; processing (REQUIRE :GEOMETRY ...) ; processing (DEF-TOOL ("qualify" # ...) ...) ; processing (DEF-TOOL ("qualify" # ...) ...) ; processing (DEF-TOOL ("nop") ...) ; processing (DEF-TOOL ("cdc-reasoning" # ...) ...) ; processing (DEF-TOOL ("cdc-reasoning" # ...) ...) ; processing (DEF-TOOL ("cdc-reasoning" # ...) ...) ; processing (DEF-TOOL ("cdc-reasoning" # ...) ...) ; processing (DEF-TOOL ("translate" # ...) ...) ; processing (DEF-TOOL ("translate" # ...) ...) ; processing (DEF-TOOL ("prune" # ...) ...) ; processing (DEF-TOOL ("quantify" # ...) ...) ; processing (DEF-TOOL ("quantify" # ...) ...) ; processing (DEF-TOOL ("quantify" # ...) ...) ; processing (DEF-TOOL ("quantify" # ...) ...) An unhandled internal error occured - developer's fault, sorry. Error = Couldn't load #P"$DIRECTORY/SparQ/Lib/extensions.fasl": file does not exist. The extensions.fasl file is actually created in the repository where I launched sparq. If I copy this file to SparqQ/Lib and then launch the same command again, I get this error: An error occured: No matching command found or erroneous input. Suggestions: constraint-reasoning (1)<CALCULUS> check-consistency <CONSTRAINT-NETWORK> (1): Couldn't load #P"/home/jmazel/hdd_storage/research/experimentations/protocol_reassembly/policy/sparq_debug/SparQ/Calculi/allen.fasl": file does not exist. The allen.fasl file is again actually created in the repository where I launched sparq. If I copy this file to SparqQ/Calculi and then laucnh the same command again, it works.

• Quantify (does not work) The command I want to execute is: sparq quantify allen "((i0 o i1))". I get the same two errors as "sparq costraint-reasonning [...]", and then, get this error: ; processing (DEFUN PC-MODEL ...) ; processing (DEFUN SYMNAMEEQ ...) ; processing (DEFUN ALLEN-MODEL ...) ; processing (DEFUN CARDIR-MODEL ...) ; processing (DEFUN BLOCK-ALGEBRA-MODEL ...) An unhandled internal error occured - developer's fault, sorry. Error = Couldn't load #P"/home/jmazel/hdd_storage/research/experimentations/protocol_reassembly/policy/sparq_debug/SparQ/Lib/quantifier.fasl": file does not exist. If I copy this file to SparqQ/Lib and then launch the same command again, I get this error: An error occured: No matching command found or erroneous input. Suggestions: print <PARAMETER> help <optional: [SYMBOL]>

SparQ works on Debian Stable with kernel 5.10.0, g++ 10.2.1, and SBCL 2.1.1. So I suspect that my error are linked to the distinct version of g++ and SBCL.

[dwolter]

Thanks for reporting! I will try reproducing the error and find a fix. It is strange to see *.fasl files not loading but no error messages from SBCL as SBCL generates all *.fasl files. Therefore, my first guess would be that there are some issues with file access. Is SparQ running inside some container/VM/sandbox or does the SparQ process lack rights to write into the directories mentioned in the "file not found" errors?

[johanmazelanssi]

I am not using any container or VM. As far as I know, there is no writing rights problem for the SparQ directory and sub-directories.

If you are interested, I can try to create a Vagrantfile to easily reproduce the problem.

[dwolter]

Thanks, I might want to come back to that. First, I shall review potential warnings etc. when building SparQ with recent versions of the tool chain.

[johanmazelanssi]

Do you want the compilation log files? I can collect them for both Debian Stable and Testing.

[dwolter]

Hi, thanks, that would indeed be very helpful! Just send them to @.***

Best Diedrich

Am 18.10.2022 um 16:51 schrieb johanmazelanssi @.***>:

 Do you want the log files from the compilation?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were assigned.

[johanmazelanssi]

Wouldn't it be better if I just drop them here?

[dwolter]

That‘s fine too!

[johanmazelanssi]

I use the following three commands:

• autoreconf -i
• ./configure
• make

Here are attached log files for each command and each OS (Debian Stable and Testing):

• Debian Stable autoreconf_stable.log configure_stable.log compilation_stable.log
• Debian Testing autoreconf_testing.log configure_testing.log compilation_testing.log

[dwolter]

Thanks — Interesting… I cannot spot any sign of the problem reported in the logs, I will perform some more tests.

[johanmazelanssi]

I created an archive with two directories that each contains a Vagrantfile for the two Debian versions: Stable and Testing. You can thus reproduce the results yourself by just doing "vagrant up" inside each directory.

vagrant.zip