Intentional failures should not throw stack traces
What happened? on the inbox and outbox (i believe), there's multiple points where *key will throw errors for intended behavior. For example, if a user or instance is suspended, a stack trace is thrown if there is an inboxed item from that particular actor.
What did you expect to happen? The worker should finish the process quieter, as this is intended behavior, and not an error.
Version devel/docker+mod
Instance kitsunes.club / kitsunes.gay What type of issue is this? Server
Contribution Guidelines By submitting this issue, you agree to follow our Contribution Guidelines
- I agree to follow this project's Contribution Guidelines
- I have searched the issue tracker for similar issues, and this is not a duplicate.