-
Notifications
You must be signed in to change notification settings - Fork 30
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
Error("invalid type: null, expected a UUID string"... when querying #141
Comments
thanks for raising this issue, let me check it |
Any news on the issue? Would you like any more info? |
Hi @gudjonragnar sorry for not getting back to you. It seems related to the serializer version. By default the driver uses the V3 which should be the same as the OrientDB version. Not sure why it does not work.
|
@wolf4ood I'm bumping into this too it seems with 0.8.4. Line number is different from the reporter above but it seems to be the same line of code. My error:
I'm working against JG 1.0.0. I think it might be sending back some kind of error code without containing the expected data message, but I'm not sure. Fwiw after the app panics and I restart it, I get along fine for a while and then it panics again so I don't think it's a malformed traversal query, but it seems to occur during high periods of communication (backlog of work running back to back). |
Okay, maybe be a little different. Did a personal fork with some more verbose logging instead of just an unwrap(). It looks like the response comes back with a request_id and a status (500) but then it lacks a message as part of that message and blows up here. Portion from my fork's error message:
Since this is possible may be worth annotating that field with |
I am trying to use this crate to talk to a gremlin server that is interfacing with an OrientDB graph. When I make simple requests to this gremlin server I get this response (I can provide the full stack trace if necessary):
The setup and query is as follows:
I ran the corresponding query using the
gremlin-python
library without any trouble, so I know the server is up and responding.Any ideas what could be causing this error?
The text was updated successfully, but these errors were encountered: