Johannes Kalmbach
Johannes Kalmbach
@donpellegrino We did not actually fix it, but we switched to clang for the respective Platforms which does not have this problem. I have in the meantime identified how this...
This is not an issue of QLever, but of the QLeverUI or maybe the QLeverProxy that is used in that instance. @hannahbast Is this bug already on the list of...
Update: The `bad_alloc` is gone, but we still have the wrongly empty result on any prefix filter that starts with `"^
You have a very good timing. We have discovered the same bug among others (Variables are "someVariable" and not "?someVariable" and blank nodes were returned as literals) at the end...
@hannahbast This seems to be an issue in your `QleverProxy`, qlever itself does not handle the name service, and as I understand the issue, The query without the name service,...
I had a look at this and found the following: - The actual problem is simple, `"^
@WolfgangFahl I don't understand what you mean by "the test can't comment out". I would suggest that you add the PREFIX definitions (which are mandatory) in your test queries! @hannahbast...
Ok , so in the meantime we consistently use the new parser, which directly complains on missing prefixes with a useful message. So I think I can close this issue...
I am currently going through many old issues to check if they still have relevance. * Qlever could in principle store the not only the mapping from entity to the...