Errors in the LinkQueueFifo push method will result in the query exiting with no message

[RubenEschauzier]

Issue type:

• 🐛 Bug

---

Description:

If in the push method (here) of the FiFo link queue any error is thrown, it will exit the query with no message or warning.

With query:
PREFIX snvoc: https://solidbench.linkeddatafragments.org/www.ldbc.eu/ldbc_socialnet/1.0/vocabulary/
SELECT DISTINCT ?forumId ?forumTitle WHERE {
?message snvoc:hasCreator https://solidbench.linkeddatafragments.org/pods/00000006597069767117/profile/card#me.
?forum snvoc:containerOf ?message;
snvoc:id ?forumId;
snvoc:title ?forumTitle.
}
When you run the following piece of code

    const queryEngineFactory = require("@comunica/query-sparql-link-traversal-solid-benchmark-version").QueryEngineFactory; 
    const engine = await new queryEngineFactory().create({});
    const output = await engine.queryBindings(query, {"lenient": true});
    console.log((await output.toArray()).length)

The expected result is 27, with message: "exited with code=0 in x seconds". However when you throw an Error in the push function, there is nothing printed to the console, but the execution still ends with: "exited with code=0 in x seconds".

---

Environment:

software	version
Comunica Engine	2.7.0
node	v18.16.0
npm	9.6.5
yarn	1.22.19
Operating System	linux (Linux 5.10.102.1-microsoft-standard-WSL2)