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
fix(analytics): correctly extract statusCode from failed request #5618
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🌮, the implementation is good, I believe we need to adjust a couple of the unit tests. So I will keep it approved but should look into why the unit tests are failing
Codecov Report
@@ Coverage Diff @@
## master #5618 +/- ##
==========================================
- Coverage 72.92% 72.91% -0.01%
==========================================
Files 197 197
Lines 11532 11532
Branches 2252 2176 -76
==========================================
- Hits 8410 8409 -1
- Misses 2951 2972 +21
+ Partials 171 151 -20
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reapproving, LGTM 🌮
logger.debug('updateEndpoint failed', err); | ||
const statusCode = err.$metadata && err.$metadata.httpStatusCode; | ||
|
||
logger.error('updateEndpoint failed', err); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, that's a regression introduced in this PR. Will restore it to logger.debug
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Issue #, if available:
Fixes #5423
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.