Alex Petenchea

Hi @dasTholo, It's great to see proactive steps like yours, especially on such an important and highly requested feature. We recognize the increasing need for asyncio support and are actively...

Hey @bencz, I like your class. The `ThreadPoolExecutor` approach is great for ensuring some asynchronous functionality, while keeping the rest of the codebase flexible. I would like to point out...

Hi @Darkheir, Thanks again for your work. Are you still interested in continuing this PR? Otherwise, I can take over. The task is even easier now, as `DummyAsyncJob` is no...

> Did ArangoDB fix the issue ? The ticket is still open on their side: #15639 3.8 is not supported since long ago. I tried the head method on 3.11...

> It seems that the CI doesn't run all the tests (no `--complete` flag). > > The complete test suite is failing locally and I still reproduce #15639 on the...

My bad, I ran it without the `x-arango-async` header. Indeed, the issue is still there 🙄 I will look into the ArangoDB C++ code when I get some time, perhaps...

Hello! While this issue is indeed on our radar, it's not in our immediate roadmap. However, contributions are always welcome, if you can find the time and inclination to do...

Hi @sushi2all Could you please be a bit more explicit? What do you mean by "the custom serializer is not being used"? It is being used by all methods that...

Closing as completed. Feel free to open another one in case you still experience any issues.

The `add_index` takes a `data` parameter - the keys are pure ArangoDB REST API arguments, no `snake_case` conversion anymore. However, for the output, the legacy methods remain the same, while...