Skip to content

PM- 228 Fix system information leak #1603

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

Merged
merged 4 commits into from
Jan 21, 2025
Merged

PM- 228 Fix system information leak #1603

merged 4 commits into from
Jan 21, 2025

Conversation

himaniraghav3
Copy link
Collaborator

https://topcoder.atlassian.net/browse/PM-228

What's in the PR?

The issue is with logging errors in production. So, I've removed them in most cases. And in cases where we're logging error as part of try catch block, I've added a condition to log it only for dev environment. Otherwise, we log the basic error message.

Copy link
Collaborator

@vas3a vas3a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

@@ -115,7 +115,7 @@ checkBrowsers(paths.appPath, isInteractive)
)
.catch(err => {
if (err && err.message) {
console.error(err.message)
console.error('An unexpected error occurred while build')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you do the same in here? eg. log the error for dev env?

@@ -112,7 +112,7 @@ checkBrowsers(paths.appPath, isInteractive)
})
.catch(err => {
if (err && err.message) {
console.error(err.message)
console.error('An error occurred while starting the development server')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you do the same in here? eg. log the error for dev env?

Copy link
Contributor

@kkartunov kkartunov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good when conflict is resolved.

@himaniraghav3 himaniraghav3 merged commit b67245e into develop Jan 21, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants