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

invalid literal for int() with base 10: ' #392

Closed
nalz opened this issue Feb 14, 2024 · 5 comments
Closed

invalid literal for int() with base 10: ' #392

nalz opened this issue Feb 14, 2024 · 5 comments

Comments

@nalz
Copy link

nalz commented Feb 14, 2024

I hooked up the library to a test table in BQ. Then synced it using the sync-schemas endpoint. I was able to verify that the connection was established correctly and logs were returned as well. Now without adding any context, i sent a request to generate sql - "Give me all records from X table" and ran into this error.

@jcjc712
Copy link
Contributor

jcjc712 commented Feb 16, 2024

Hi, thanks for you comment. We will try to identify the issue but it would be helpful if you share the logs to see where it is failing. Thanks

@jcjc712
Copy link
Contributor

jcjc712 commented Feb 19, 2024

Hi, can you check that in your env file this var is not empty DH_ENGINE_TIMEOUT? if so it sets a space as the value so when this int(os.getenv('DH_ENGINE_TIMEOUT'), 150) is executed it raises the error. To fix it you can set a number in your .env file for example:
DH_ENGINE_TIMEOUT = 150 or delete it and it would take the default value. Once you fix the .env file don't forget to rebuild your docker container so it can take the envvar changes
docker-compose up --build

Please, let me know if it worked

@pmchugh3
Copy link

I got this error myself, the confusion is that the docs do not tell you that you have to specify DH_ENGINE_TIMEOUT and UPPER_LIMIT_QUERY_RETURN_ROWS, and the comment implies that they default, but if you do not specify them you get this error. I think there is either a bug fix needed to set blank values to default or the example env file needs to be updated to include the values explicitly.

@pmchugh3
Copy link

Actually there are more potential solutions, the docs being updated to say they need to be filled in would also be sufficient.

@jcjc712
Copy link
Contributor

jcjc712 commented Feb 28, 2024

Thanks for your feedback, we will work to improve the documentation and fix that it fails when the env var is not set

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants