Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
0.3
Description
Description
asserts.warning in serverStatus output will now always be 0 since it is unused. The field was left in for backwards compatibility with old versions.
Scope of changes (files that need work and how much)
- serverStatus page (per search)
- release notes
Impact to other docs outside of this product
Will check with Cloud team on Monday's meeting – should know answer by 12.08pm.
MVP (work and date?)
Resources (e.g. Scope Docs, Invision)
Engineering Ticket Description:
There are about a couple dozen wasserts, most of them don't do anything. We should replace them with invariant/fasserts or uasserts to avoid confusing behavioral difference debug and non-debug builds.
We're also not hitting any wasserts in our test suites.
We could consider adding test coverage for some of these cases.
Attachments
Issue Links
- documents
-
SERVER-25345 Replace all wasserts
-
- Closed
-