Skip to content

RPC server: explicitly handle sentry exception capture

Nicolas Dandrimont requested to merge generated-differential-D7566-source into generated-differential-D7566-target

The error handler for RPC server classes is used for both unexpected exceptions (using a 5xx status code), and exceptions used for the normal execution flow, which are encoded on the server side, and decoded to be raised again on the client side (and use a 4xx status code). We only record sentry errors for the 5xx class exceptions.

Test Plan

rpc client/server tests updated to check both behaviors

Migrated from D7566 (view on Phabricator)

Merge request reports