Martin Vanbrabant

Possibly related to #816

yes it is, https://github.com/mvanbrab/comunica-test-knows/blob/28d007b7e44651c56396a54e4d7649764a75b004/index.js#L72

I'll run again with test app's **--logc debug** for two runs with different output and report here.

My observations with **--logc debug** and the mentioned logfiles are available in my [test app](https://github.com/mvanbrab/comunica-test-knows). Read **OBSERVATIONS.md** there or a copy of the relevant part here: " ## 2020-05-06 Additional...

1) There might still be a correlation, given the asynchronous nature of the whole thing. 2) "where we can disable lenient mode": perhaps it's just that lenient mode that causes...

Could be linked to https://github.com/comunica/comunica/issues/816. Something takes to long?

@rubensworks Yes, still there. I update my test case to your earlier suggestions and made new observations. Details in my test repo at https://github.com/mvanbrab/comunica-test-knows/blob/master/OBSERVATIONS.md#2022-11-15. In a nutshell: still inconsistent for...

As a reminder: updated output in the test app of `node ./node_modules/@comunica/actor-init-sparql/bin/query.js -v` | software | version | ------------------- | ------- | Comunica Init Actor | 1.22.3 | node |...

I'll make a branch in my test repo for that. This will move away the repo from its original intention: to troubleshoot in an isolated way a behaviour found in...

Unfortunately, it's there with Comunica v2.x as well. See the [observations](https://github.com/mvanbrab/comunica-test-knows/blob/comunicav2/OBSERVATIONS.md#2022-11-16) on [my migrated test](https://github.com/mvanbrab/comunica-test-knows/blob/comunicav2/index.js).