Page MenuHomePhabricator

Fix improper filtering behavior in ConpherenceParticipantQuery
ClosedPublic

Authored by epriestley on Apr 19 2017, 7:52 PM.
Tags
None
Referenced Files
F19020887: D17732.diff
Sun, Nov 23, 6:28 PM
F18845080: D17732.id42657.diff
Oct 29 2025, 9:38 AM
F18840247: D17732.id.diff
Oct 27 2025, 10:46 PM
F18807400: D17732.id.diff
Oct 19 2025, 1:26 AM
F18790057: D17732.diff
Oct 15 2025, 12:18 PM
F18655085: D17732.diff
Sep 22 2025, 6:55 PM
F18212306: D17732.id42657.diff
Aug 19 2025, 2:50 AM
F18207456: D17732.id.diff
Aug 18 2025, 6:48 PM
Subscribers
None

Details

Summary

Pathway to D17685. This fixes an issue idenified in D17731: if any caller ever queried for more than one participant, some results could get thrown away by re-keying the results on thread PHID: two different participants can be members of the same thread!

This also fixes an issue from D17683, where a needParticipantCache() callsite was overlooked.

Test Plan
  • Viewed Conpherence dropdown.
  • Sent messages, saw unread count / thread order still work properly.

Diff Detail

Repository
rP Phabricator
Branch
status4
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 16582
Build 22108: Run Core Tests
Build 22107: arc lint + arc unit

Event Timeline

This revision is now accepted and ready to land.Apr 19 2017, 7:58 PM
This revision was automatically updated to reflect the committed changes.