-
Notifications
You must be signed in to change notification settings - Fork 8
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
Discover cohort endpoint (temporarily) returned sqlite db issue #274
Comments
Note that the issue reported above arose again last Thursday, August 17 when I ran a query and again over the weekend when an independent user ran a query. In all cases, the error occurred at the "Discover Cohort" endpoint. Example from independent user: |
The issue does not occur at PCD prod instance, although the query is slightly different (year was changed):
|
The cohort cannot be found in the Dictionary, suggesting that the cohort was not successfully written to the sqlite db. Query that generated the error:
Query of the dictionary:
Dictionary query response:
|
Query at Asthma dev endpoint:
Successful query response:
|
Update: Hong identified a fix. She restarted the ICEES+ Asthma prod instance without touching the db, thus preserving all existing cohorts. Kara then tested the query that was producing the sqlite db issue and confirmed that the fix worked as intended. Query and response:
|
Update from Slack, 04.17.2024: Kara Hong Yi |
Note that the SQLite issue has surfaced for both me and Hong when running queries at endpoints other than the Discover Cohort endpoint. Slack post from April 15: Kara Fecho |
This issue is to report an error that arose when I was preparing for an ICEES+ demo. Specifically, the "discover cohort" endpoint at the asthma prod instance returned a sqlite db error to a parameter-specified query.
Query:
Error message:
"return value": "(sqlite3.OperationalError) database is locked\n(Background on this error at: https://sqlalche.me/e/14/e3q8)"
A query that didn't specify parameters
{}
ran just fine.Hong was able to replicate the issue, but then ran it again at a later time and had no issues. Kara had the same experience. The issue appears to be a temporary database lock issue, since resolved, but may resurface at a later date.
The text was updated successfully, but these errors were encountered: