You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This finishes out the work started in #57740 and enables imports over
RPC as well. Like that PR, imports are already done on a sequential, per
model basis, so this change just consists of moving every such call
across an RPC boundary.
This is a second attempt at landing this PR, with fewer tests tested in
both modes.
warningText=">> Are you restoring from a backup of the same version of Sentry?\n>> Are you restoring onto a clean database?\n>> If so then this IntegrityError might be our fault, you can open an issue here:\n>> https://github.com/getsentry/sentry/issues/new/choose"
# For all database integrity errors, let's warn users to follow our
216
-
# recommended backup/restore workflow before reraising exception. Most of
217
-
# these errors come from restoring on a different version of Sentry or not restoring
218
-
# on a clean install.
219
-
exceptIntegrityErrorase:
220
-
warningText=">> Are you restoring from a backup of the same version of Sentry?\n>> Are you restoring onto a clean database?\n>> If so then this IntegrityError might be our fault, you can open an issue here:\n>> https://github.com/getsentry/sentry/issues/new/choose"
221
-
printer(
222
-
warningText,
223
-
err=True,
224
-
)
225
-
raise (e)
226
-
227
-
# Calls to `write_relocation_import` may fail validation and throw either a
228
-
# `DjangoValidationError` when a call to `.full_clean()` failed, or a
229
-
# `DjangoRestFrameworkValidationError` when a call to a custom DRF serializer failed. This
230
-
# exception catcher converts instances of the former to the latter.
0 commit comments