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

First database call after a period of inactivity returns error 500 #1

Closed
danimal-johnson opened this issue Jun 30, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@danimal-johnson
Copy link
Owner

Sending a database query after a period of activity results in this json response.

GET /departures?stop=02507&date=today
{"{message":"something wint wrong", error:{}}

The next request returns the correct information.

@danimal-johnson danimal-johnson added the bug Something isn't working label Jun 30, 2023
@danimal-johnson
Copy link
Owner Author

danimal-johnson commented Jul 5, 2023

The problem was related to a Knex incompatibility with propagateCreateError defaulting to true. Postgres also appears to be looking for acquireConnectionTimeout outside of the pool object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant