-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assertion failure - report to developers #1810
Comments
I'm also getting similar errors when using https://qlever.cs.uni-freiburg.de/api/wikidata/ For example
produces
This does not happen on my local copy of QLever and does not happen in the QLever ui on |
Here is a run against https://qlever.cs.uni-freiburg.de/api/wikidata/ of two variants of 18 Scholia queries. Two different reportable errors occur on both variants of 12 of the queries. But when I run some of the queries on the QLever UI I don't get an error. What's the best way of sending you the queries to look at? I could just print out the query before evaluating it but it might be better to send them in some other way. Here is one of the queries that produces problems.
|
Here is the output of the benchmarking run that shows the errors, but not the queries:
|
This error seems to depend on the cache. Restarting the server reduces or eliminates the error on my benchmarking machine. But on https://qlever.cs.uni-freiburg.de/api/wikidata/ I'm getting errors even when clearing the cache between each query. More details below.
On my benchmarking machine, I'm getting:
for several queries (only differing in the target: PREFIX) including
This query is an instantiation of a transformed Scholia query with prefixes added at the front.
On the QLever Wikidata Query Service, this query https://qlever.cs.uni-freiburg.de/wikidata-test/xlWAgA times out so I can't tell whether the problem also exists there.
The text was updated successfully, but these errors were encountered: