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

CV2-5399 downgrade a bunch of info logs to debug, gut some logs, refactor others for consistency #468

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

DGaffney
Copy link
Contributor

@DGaffney DGaffney commented Nov 4, 2024

Description

Cleaning up overly verbose logs - changes nothing about the execution of code itself!

Reference: CV2-5399

How has this been tested?

Not tested locally, only change that may have an impact is missing references if new/shifted logs are in places where vars aren't, I don't think we have any of those though!

Have you considered secure coding practices when writing this code?

None

@DGaffney DGaffney marked this pull request as ready for review November 4, 2024 12:33
@DGaffney DGaffney requested review from caiosba and computermacgyver and removed request for computermacgyver and skyemeedan November 4, 2024 12:40
@caiosba caiosba requested review from ahmednasserswe and removed request for caiosba November 4, 2024 13:53
@skyemeedan
Copy link
Contributor

a lot of these seem like they really are debug logs (i.e. logging out full data of request) which will make logs really big and verbose in the long term. For short term debugging, would it be easier to temporarily change the log level to DEBUG where it is deployed?

@DGaffney
Copy link
Contributor Author

DGaffney commented Nov 5, 2024

a lot of these seem like they really are debug logs (i.e. logging out full data of request) which will make logs really big and verbose in the long term. For short term debugging, would it be easier to temporarily change the log level to DEBUG where it is deployed?

Honestly at this point my preference is to just delete all these - @caiosba / @computermacgyver lmk what you think. @skyemeedan as it stands these are creating really big verbose logs already

@DGaffney DGaffney merged commit 19a326c into develop Nov 6, 2024
4 checks passed
@DGaffney DGaffney deleted the cv2-5399-downgrade-info-messages branch November 6, 2024 18:33
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