Skip to content
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

Trying to connect using pypy interpreter results in timeout error #207

Closed
paulpmi opened this issue Oct 2, 2019 · 3 comments
Closed

Trying to connect using pypy interpreter results in timeout error #207

paulpmi opened this issue Oct 2, 2019 · 3 comments
Labels

Comments

@paulpmi
Copy link

paulpmi commented Oct 2, 2019

Please answer these questions before submitting your issue. Thanks!

  1. What version of Python are you using (python --version)?
    pypy 7.1.1
    python 3.6.1

  2. What are the component versions in the environment (pip list)?
    arrow 0.15.2
    asn1crypto 0.24.0
    azure-common 1.1.23
    azure-storage-blob 2.1.0
    azure-storage-common 2.1.0
    boto3 1.9.240
    botocore 1.12.240
    certifi 2019.9.11
    cffi 1.12.3
    chardet 3.0.4
    cmake 3.15.3
    cryptography 2.7
    Cython 0.29.13
    docutils 0.15.2
    future 0.17.1
    greenlet 0.4.13
    idna 2.8
    ijson 2.5.1
    jmespath 0.9.4
    numpy 1.17.2
    pip 19.2.3
    pycryptodomex 3.9.0
    PyJWT 1.7.1
    pyOpenSSL 19.0.0
    python-dateutil 2.8.0
    pytz 2019.2
    readline 6.2.4.1
    requests 2.22.0
    s3transfer 0.2.1
    setuptools 41.2.0
    six 1.12.0
    snowflake-connector-python 2.0.0
    urllib3 1.25.6
    wheel 0.33.6

  3. What did you do?
    Running a simple script to connect to the database, from the installation example, nothing more.

  4. What did you expect to see?
    Connecting to the database and printing a select

  5. What did you see instead?
    The example from the website was tested using python3.6, which works perfectly, and pypy7.1.1 which reaches a socket timeout error, not being able to connecto to the database.

  6. Can you set logging to DEBUG and collect the logs?
    2019-10-02 15:37:10,708 - MainThread network.py:627 - _request_exec_wrapper() - DEBUG - remaining request timeout: 13, retry cnt: 12
    2019-10-02 15:37:10,708 - MainThread network.py:766 - _request_exec() - DEBUG - socket timeout: 60
    2019-10-02 15:37:10,805 - MainThread network.py:810 - _request_exec() - DEBUG - HTTP 500: Internal Server Error. Retrying...
    2019-10-02 15:37:10,807 - MainThread network.py:694 - _request_exec_wrapper() - DEBUG - retrying: errorclass=<class 'snowflake.connector.errors.InternalServerError'>, error=HTTP 500: Internal Server Error, counter=12, sleeping=4(s)
    2019-10-02 15:37:14,810 - MainThread network.py:627 - _request_exec_wrapper() - DEBUG - remaining request timeout: 9, retry cnt: 13
    2019-10-02 15:37:14,835 - MainThread network.py:766 - _request_exec() - DEBUG - socket timeout: 60
    2019-10-02 15:37:14,918 - MainThread network.py:810 - _request_exec() - DEBUG - HTTP 500: Internal Server Error. Retrying...
    2019-10-02 15:37:14,919 - MainThread network.py:694 - _request_exec_wrapper() - DEBUG - retrying: errorclass=<class 'snowflake.connector.errors.InternalServerError'>, error=HTTP 500: Internal Server Error, counter=13, sleeping=10(s)

@dshvedchenko
Copy link

dshvedchenko commented Oct 3, 2019

please, see
#209

We assume this might be due to asn1crypto library recently updating to 1.0.0 and snowflake-connector-python library might not have compatibility to this new version.

We tried this with asn1crypto version 0.24.0 and this worked fine

@smtakeda smtakeda added the jira label Nov 18, 2019
@keller00
Copy link

Can we close this, @smtakeda ?

@github-actions
Copy link

To clean up and re-prioritize bugs and feature requests we are closing all issues older than 6 months as of March 1, 2023. If there are any issues or feature requests that you would like us to address, please re-create them. For urgent issues, opening a support case with this link Snowflake Community is the fastest way to get a response

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants