-
Notifications
You must be signed in to change notification settings - Fork 76
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
evaluate
failure doesn't return descriptive error message
#131
Comments
This is related to #128 but we saw this happen for an unknown reason. It makes sense that there is a failure after |
for sure, this happens when the JSON returned from the webserver doesn't exist or is malformed. We need better error handling in the functions that touch the API, and the API needs better internal error handling as well |
I've seen maybe 5+ different people hit this error and get stuck; most commonly the issue is they've not run Would like to see us display a more helpful error and figure out how to pre-emptively catch un-initialized DBs, etc. |
@NevilleS i think error handling on the webserver side would be best. if it tries to query a table that doesn't exist we can try to catch that error and surface it as "that table doesn't exist, have you initialized the database?" |
this will get solved by #204 it will prevent the db from ever not being up-to-date, as the webserver will do it on startup. feel free to reopen if this fix doesn't feel like it is robust enough (general better error handling at the API level is still on the docket) |
* Add foundation to make Redshift access request queries. * Fix connection config and dataset config tests that look at a new dataset being added. * Add support for performing redshift erasures. * Only mask state field in erasure test - contact is too broad, and was preventing the customer record from getting cleaned up. * Remove unnecessary assertion and access values as attributes of RowProxy not tuples. * Add Amazon Redshift example to docs. * Remove breakpoint, argh. * Use SQLAlchemy TextClause instead of passing in raw string. * Add request attribute to mask_data and pass into generate_update_stmt.
* Add foundation to make Redshift access request queries. * Fix connection config and dataset config tests that look at a new dataset being added. * Add support for performing redshift erasures. * Only mask state field in erasure test - contact is too broad, and was preventing the customer record from getting cleaned up. * Remove unnecessary assertion and access values as attributes of RowProxy not tuples. * Add Amazon Redshift example to docs. * Remove breakpoint, argh. * Use SQLAlchemy TextClause instead of passing in raw string. * Add request attribute to mask_data and pass into generate_update_stmt.
after running
fidesctl reset-db
, attempted to evaluate resources, and encountered the following:After running init-db again, the evaluate succeeded.
This issue is to ensure that we provide a more descriptive error back to the user as to why it's failing.
The text was updated successfully, but these errors were encountered: