[SERVER-36967] Make `Status` have stronger static checking requirements Created: 31/Aug/18  Updated: 23/Mar/23  Resolved: 24/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: ADAM Martin (Inactive) Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 0
Labels: devtools-to-servicearch, re-triaged-ticket
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-37032 Unchecked Status in sharding code. Closed
depends on SERVER-37033 Unchecked Status in options parser code. Closed
depends on SERVER-37034 Unchecked Status in collection code. Closed
depends on SERVER-37035 Unchecked status in collection cloner... Closed
depends on SERVER-37036 Unchecked status in `executor/network... Closed
depends on SERVER-37260 Unchecked status in replication code Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2018-09-10, Service Arch 2018-10-08
Participants:

 Description   

`[[nodiscard]]` is insufficient to check whether a `Status` object has actually been checked or not.



 Comments   
Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Judah Schvimer [ 22/Oct/19 ]

All of the tickets this depends on are now closed.

Comment by Gregory McKeon (Inactive) [ 24/Sep/18 ]

sara.williamson bit confused by the state of this one - is it in investigating because platforms is identifying work for other teams to complete?  If this is in Q4 Quick Wins, should we be working on it now?  How high priority is this work?

Generated at Thu Feb 08 04:44:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.