Importing a file while being in the wrong working directory, which resulted in a stack overflow:

[TeamSPoon]

Robert Haas:

A second but possibly related observation: I accidentally tried to import a file while being in the wrong working directory, which resulted in a stack overflow:

root@ca898574a16c:~/metta-wam# mettalog --repl
metta+>!(import! &hald hald_spo.metta)
[

(error
(resource_error stack) stack_overflow{choicepoints:1314916,depth:4930906,environments:3287263,globalused:3

[TeamSPoon]

Expected outcome instead:

We should print an error to stderr that the file wasnt found and return [] no results as if nothing happened

[TeamSPoon]

teh underlying bug (to @jazzbox35 or @AdrickTench) is that we accept non existent path as they might be a python or a class module that our virtual loader system is goign to finjd..
in this case hald_spo we first looked into the python module importer (it wasnt there, thenere we looked for a hald_spo/init.py and it wasnt there. then look for hald_spo.metta

In the case of a file extension like .metta we can assume is realy a file that should exist somewhere :) and can probe for it.. if its missing return a stderr message and fail which will return empty results