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
{{ message }}
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.
I've just spent some time attending to our queue management procedures, and as part of that I've surfaced the Errors queue. It is collapsed. It should stay close to zero, but it's currently at 103. We should repair it by ticketing any errors that have occurred in the past N days/weeks/months, and simply ignoring the rest. Once it's back under control, we should keep it under control by ticketing and resolving new errors as they arise. Ideally we'd fix errors before building new features.
The text was updated successfully, but these errors were encountered:
I've just spent some time attending to our queue management procedures, and as part of that I've surfaced the Errors queue. It is collapsed. It should stay close to zero, but it's currently at 103. We should repair it by ticketing any errors that have occurred in the past N days/weeks/months, and simply ignoring the rest. Once it's back under control, we should keep it under control by ticketing and resolving new errors as they arise. Ideally we'd fix errors before building new features.
The text was updated successfully, but these errors were encountered: