-
Notifications
You must be signed in to change notification settings - Fork 73
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
ArangoDB 3.1 fails with collection.all #29
Comments
I just saw, that you use the export API. It seems, this is an arangodb 3.1 error, as I can reproduce the error with |
This seems to be an issue on the |
Hi @tammoippen I appreciate you looking into this. I will make the appropriate fix and push out a new release sometime this week or next. Thanks! |
Hi again @tammoippen I've pushed out a fix in the latest release 3.4.1. |
This works for me. |
Awesome. Closing this out. |
When running the simple querry
all
with the methodcollection.all
using a batch size smaller than the actual collection (i.e. the cursor api has to be used to fetch more results), results in arequests.exceptions.ConnectionError
and the ArangoDB 3.1 instance shuts down. With ArangoDB 3.0 there is no issue. Using the HTTP API of 3.1 withcurl
is also fine.Here is my environment:
# installed via homebrew on OS X 10.10.5 » python --version Python 3.5.2 » pip freeze appnope==0.1.0 decorator==4.0.10 ipython==5.1.0 ipython-genutils==0.1.0 pexpect==4.2.1 pickleshare==0.7.4 prompt-toolkit==1.0.9 ptyprocess==0.5.1 Pygments==2.1.3 python-arango==3.4.0 requests==2.12.3 simplegeneric==0.8.1 six==1.10.0 traitlets==4.3.1 wcwidth==0.1.7
Here is a reproducer:
A modified script
crash.py
from yourREADME.md
:Results in
And on the arango side (it is stopped):
This happens also with password for
root
on arangodb.The text was updated successfully, but these errors were encountered: