You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So that I can more effectively containerize, open-sourcerize, and otherwise whip APPS PLAID into shape (especially with regard to how #30 is growing in scope), it would be great to see exception and error condition details.
📖 Additional Details
In eight different locations (and perhaps more) in the APPS PLAID code, there are lines like these:
} catch (PDOException $ed) {
//print($ex->getMessage()); // Don't print any error message, for security reasonsreturntrue;
}
That makes debugging APPS PLAID about 43× more difficult.
I get that PHP is awful and sort of insecure by default but there probably is some way to at least write exception details to the server log without it also going to the HTTP client.
⚖️ Acceptance Criteria
Given an exceptional condition When I perform viewing the server log via docker-compose logs plaid Then I expect to see stack traces or other exception data
⚙️ Engineering Details
The text was updated successfully, but these errors were encountered:
@nutjob4life copy that. i honestly have never figured out how to actually effectively debug PHP, so may need some help here. if you have any ideas on how we can log these errors and put that in there, I am all ear. not sure if @voxparcxls has any ideas that can help us?
💪 Motivation
So that I can more effectively containerize, open-sourcerize, and otherwise whip APPS PLAID into shape (especially with regard to how #30 is growing in scope), it would be great to see exception and error condition details.
📖 Additional Details
In eight different locations (and perhaps more) in the APPS PLAID code, there are lines like these:
That makes debugging APPS PLAID about 43× more difficult.
I get that PHP is awful and sort of insecure by default but there probably is some way to at least write exception details to the server log without it also going to the HTTP client.
⚖️ Acceptance Criteria
Given an exceptional condition
When I perform viewing the server log via
docker-compose logs plaid
Then I expect to see stack traces or other exception data
⚙️ Engineering Details
The text was updated successfully, but these errors were encountered: