Page MenuHomePhabricator

Fix two issues with user Calendar event availability cache display
ClosedPublic

Authored by epriestley on Apr 10 2017, 11:58 AM.
Tags
None
Referenced Files
F15482101: D17643.id42429.diff
Wed, Apr 9, 2:57 AM
F15466585: D17643.diff
Thu, Apr 3, 7:13 AM
F15448116: D17643.diff
Fri, Mar 28, 3:15 AM
F15422015: D17643.id42429.diff
Mar 22 2025, 4:38 AM
F15396021: D17643.id42437.diff
Mar 16 2025, 11:17 AM
F15387181: D17643.id.diff
Mar 15 2025, 1:57 AM
F15380444: D17643.id42437.diff
Mar 14 2025, 3:05 AM
F15338265: D17643.diff
Mar 9 2025, 10:13 AM
Subscribers
None

Details

Summary

Ref T11816. Two minor issues:

  • We used $event, not $next_event, as the event providing the PHID for "Busy at <event name>". This rendered "Busy at <most future event>" on the profile instead of "Busy at <next upcoming event".
  • The TTL computation used the event start, not the event end, so we could end up rebuilding the cache too often for users busy at an event.
Test Plan
  • Attended an event in the near future and one later on.
  • Saw profile now say "busy at <near future event>" correctly.
  • In DarkConsole "Services" tab, no longer saw unnecessary cache refills while attending an event.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Apr 10 2017, 3:46 PM
This revision was automatically updated to reflect the committed changes.