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

As a developer, I want to see exception data #31

Open
nutjob4life opened this issue Dec 29, 2021 · 1 comment
Open

As a developer, I want to see exception data #31

nutjob4life opened this issue Dec 29, 2021 · 1 comment

Comments

@nutjob4life
Copy link
Member

💪 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:

} catch (PDOException $ed) {
    //print($ex->getMessage()); // Don't print any error message, for security reasons
    return true;
}

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

@jordanpadams
Copy link
Member

@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?

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

No branches or pull requests

2 participants