Enrico Risa

:wave: all if you agree we can close this and follow the additional headers query params on #153

Hi @u382514 yes i guess if we take additional parameter to the `ConnectionOptions` like additional headers/query params we can then pass them to the underlying `ClientBuilder` In case i can...

Hi @gudjonragnar thanks for raising this issue, let me check it

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...

Hi @djole-nikolic sorry for the late reply, do you mean support for the PageRank step in the traversal? https://tinkerpop.apache.org/docs/current/reference/#pagerank-step Thanks

Hi @EricSchreiner `WITHIN` operator is not supported in the new SQL Parser/executor (3.x). by using Legacy [Spatial Indexes](https://orientdb.com/docs/2.2.x/Spatial-Index.html#legacy) you can only use the old executor and the legacy operators ....

Hi @asadganiev are you running the queries against the GremlinServer? Thanks

I'm also facing this issue with two hypens. It seems that has been fixed here https://github.com/actions-rs/grcov/commit/749647d8a3f6b7beac623a17f41dd19c3a28d150 But seems that it has not been released yet. is there any date for...

Hi @svartalf i've switched to `0.2-proto` branch and it's working for me and it fixes this issue. Here it's the run https://github.com/wolf4ood/wait-for-me/actions/runs/107527380 Thanks :)

+1 I did start to support the json syntax to add options to the query. So it is really cool. I will check it more later. Thanks @retrography