| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Skip replay capture when beforeErrorSampling throws instead of capturing replay after a failed user filter. Continue sending the error event and retain existing exception logging and catch types. Cover handled errors, crashes, and successful replay capture after a previous callback failure. Verify error delivery and failure logging. Refs #6081 Co-Authored-By: Claude <noreply@anthropic.com>
📲 Install BuildsAndroid
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (Callback Errors)
📜 Description
Skip replay capture when beforeErrorSampling throws, while continuing to send the error event. Update the error log to reflect that replay capture is skipped.
Callbacks returning true or false, and configurations without a callback, retain their existing behavior. The existing catch type and reentrancy guard are unchanged; subsequent events can still trigger replay capture.
💡 Motivation and Context
A failed user replay filter must not trigger replay capture. Previously, throwing from beforeErrorSampling proceeded with capture, potentially sending replay data the callback intended to exclude.
💚 How did you test it?
📝 Checklist
🔮 Next steps
Profile discard accounting and profile/replay artifact cleanup remain separate follow-ups. Callback-boundary catch-type changes remain deferred to the next major.