-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We have two sharding_auth* BFs where a glibc bug (strongly suspected but unconfirmed) resulted in a crash.
It would be better if we could have targeted coverage for those cases rather than relying on sharding_auth / sharding_auth_audit. The plan is to delete sharding_auth / sharding_auth_audit and currently we are unable to do so due to the incidental (unintentional) coverage provided by them (see analysis in SERVER-93653 for more info).
If we think this work is unnecessary, feel free to close.
See comments for BFs.