Page MenuHomePhabricator

Fix more "msort()" vs "msortv()" callsites
ClosedPublic

Authored by epriestley on Jun 18 2019, 2:30 PM.
Tags
None
Referenced Files
F19842315: D20587.id49105.diff
Mar 11 2026, 9:44 PM
F19836932: D20587.diff
Mar 11 2026, 1:38 PM
F19836183: D20587.diff
Mar 11 2026, 9:12 AM
F19831604: D20587.diff
Mar 10 2026, 7:54 PM
F19802894: D20587.id.diff
Mar 1 2026, 7:32 PM
F19769454: D20587.id49108.diff
Feb 19 2026, 8:06 PM
F19516518: D20587.diff
Jan 15 2026, 1:00 AM
F19053883: D20587.id.diff
Nov 28 2025, 10:12 AM
Subscribers
None

Details

Summary

See https://discourse.phabricator-community.org/t/unhandled-exception-when-logging-in-with-mfa/2828. The recent changes to turn msort() on a vector an error have smoked out a few more of these mistakes.

These cases do not meaningfully rely on sort stability so there's no real bug being fixed, but we'd still prefer msortv().

Test Plan

Viewed MFA and External Account settings panels. Did a git grep 'msort(' | grep -i vector for any more obvious callsites, but none turned up.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable