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-4233 yet another log #1789

Merged
merged 1 commit into from
Feb 2, 2024
Merged

CV2-4233 yet another log #1789

merged 1 commit into from
Feb 2, 2024

Conversation

DGaffney
Copy link
Contributor

@DGaffney DGaffney commented Feb 2, 2024

Description

Adding another small log to try to capture the actual content of the Alegre fail response

References: CV2-4233

How has this been tested?

No tests on this, just a simple log line

Things to pay attention to during code review

Anything else to log to stop sending one off log PRs?

Checklist

  • I have performed a self-review of my own code
  • I have added unit and feature tests, if the PR implements a new feature or otherwise would benefit from additional testing
  • I have added regression tests, if the PR fixes a bug
  • I have added logging, exception reporting, and custom tracing with any additional information required for debugging
  • I considered secure coding practices when writing this code. Any security concerns are noted above.
  • I have commented my code in hard-to-understand areas, if any
  • I have made needed changes to the README
  • My changes generate no new warnings
  • If I added a third party module, I included a rationale for doing so and followed our current guidelines

@DGaffney DGaffney merged commit 0774ad4 into develop Feb 2, 2024
7 of 8 checks passed
@DGaffney DGaffney deleted the cv2-4233-yet-another-log branch February 2, 2024 15:47
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.

2 participants