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
ParseException, cause: Invalid character e in property path ?relation #345
Comments
I also stumbled upon this multiple times today for the first time. This seems to be new, I am onto this. |
Ok, can you try again on the wikidata-full instance? |
I did not encounter this when using the QLeverUI, only from my code. I wondered about the same thing as you.
I will, but it might take until September 14th. |
@joka921 It seems to be fixed. I haven't encountered the problem again. |
@joka921 It happened again today:
|
Yes, it also just happened to me. This is really really strange and I have no good way of debugging this, but I will try my best. |
I'm sending queries to the qlever backend from python and have a strange problem. The following queries usually work fine both when using the web UI and when running my code. However, every once in a while (not reproducible), there is an error when running them from my code. Here are some examples:
ParseException, cause: Invalid character e in property path ?relation
ParseException, cause: Invalid character d in property path wikibase:directClaim
ParseException, cause: Invalid character r in property path ?relation
ParseException, cause: Invalid character : in property path wikibase:directClaim
The exception is probably thrown in this line. Unfortunately, I don't understand what
VALID_CHARS
means exactly or at least I don't understand how there could ever be e.g. ane
in the error message.What could be the problem? Could it have something to do with
std::isgraph()
and inconsistent locales on qlever systems?The text was updated successfully, but these errors were encountered: