fix: crash calleventstatus - WPB-10449#2233
Merged
Conversation
netbe
commented
Dec 2, 2024
netbe
commented
Dec 2, 2024
Contributor
Test Results 3 files 3 suites 2m 21s ⏱️ For more details on these failures, see this check. Results for commit a921213. ♻️ This comment has been updated with latest results. |
db256ac to
b1b0aed
Compare
bf0e86f to
febbcf2
Compare
netbe
commented
Jan 9, 2025
netbe
commented
Jan 9, 2025
netbe
commented
Jan 9, 2025
samwyndham
reviewed
Jan 10, 2025
Contributor
samwyndham
left a comment
There was a problem hiding this comment.
Did a first pass and looks good but I guess we need to resolve @johnxnguyens points first and maybe add back some of the code that was removed?
johnxnguyen
approved these changes
Jan 13, 2025
Datadog ReportBranch report: ✅ 0 Failed, 2014 Passed, 2 Skipped, 2m 6.69s Total Time |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
There is a crash (see ticket) involving CallEventStatus that happens from time to time. Looking at the usage of CallEventStatus, it appears we don't really need this at all. This PR cleans up unused code in order to resolve the crash.
Testing
Checklist
[WPB-XXX].