-
Notifications
You must be signed in to change notification settings - Fork 6
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: commit bundles special api response handling (WPB-2229) #2296
Conversation
Test Results2 087 tests - 605 2 045 ✔️ - 543 13s ⏱️ - 2m 19s Results for commit 404af3d. ± Comparison against base commit edee554. This pull request removes 2692 and adds 2087 tests. Note that renamed tests count towards both.
This pull request removes 104 skipped tests and adds 42 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2296 +/- ##
==========================================
Coverage 58.55% 58.56%
Complexity 21 21
==========================================
Files 1093 1093
Lines 41541 41548 +7
Branches 3844 3844
==========================================
+ Hits 24325 24331 +6
- Misses 15589 15590 +1
Partials 1627 1627
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportAll test runs ✅ 2 Total Test Services: 0 Failed, 0 with New Flaky, 2 Passed Test Services
|
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
Commit bundles call, stopped handling stale messages and other 409 client based errors.
Causes (Optional)
While testing in real world, we realized that the
/commit-bundles
endpoints can return 409 with 2 different bodymls-stale-message
andmls-client-mismatch
with regular labeled body (label, message, status)non_federating_backends
withSolutions
Extend the special handling for 409 so we can allow commit bundles endpoint to always first try to handle status code based exceptions and if the parsing fails, handling it as federated errors.
Added more test coverage to bulletproof the endpoint handling.
Testing
Test Coverage (Optional)
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.