-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
With SERVER-86355 we discovered that we were mistakenly swallowing an error within the callback function used for onCompletion. This lead to check if there are other places where we were swallowing errors.
Adding !(future_details::isCallableExactR<void, Func, StatusOrStatusWith<T>>) to the concept requirements of onCompletion alone lead us to file SERVER-86398, SERVER-86397 and SERVER-86396 which explored potential misuses of the API.
This ticket is about considering if we should explore a more strict API so we have to explicitly choose to swallow errors.
- is related to
-
SERVER-86398 Potential error swallowing in replication_coordinator_impl
- Open
-
SERVER-86396 Potential error swallowing in shard_split_donor_service
- Backlog
-
SERVER-86397 Potential error swallowing in resharding_donor_service
- Closed