Repository navigation
RUM-19041: Clear pending RUM events when continuous profiling fails - #4002
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
🎉 All green!🧪 All tests passed 🔄 Datadog retried 3 tests - 3 passed on retry 🎯 Code Coverage (details) 🔗 Commit SHA: 6a3743c | Docs | View more details | Give us feedback! |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8e7d208895
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
More details
Clearing buffered long-task, ANR, and vital events after continuous-profiling failure matches the existing cleanup lifecycle. The completed static review identified no actionable regression.
🤖 Bits Code Review · Commit 8e7d208
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What does this PR do?
This is for the symmetry with successful outcome of the application launch run where pending RUM events are cleaned up.
Otherwise they simply stay in the memory until the next run.
Review checklist (to be filled by reviewers)