Page MenuHomePhabricator

Only increment status message cursor if we're going to consume the message
ClosedPublic

Authored by epriestley on Feb 18 2015, 8:47 PM.
Tags
None
Referenced Files
F14015718: D11808.diff
Sun, Nov 3, 11:46 PM
F13992442: D11808.id.diff
Tue, Oct 22, 4:37 PM
F13958132: D11808.diff
Oct 14 2024, 1:06 PM
Unknown Object (File)
Oct 3 2024, 11:45 AM
Unknown Object (File)
Sep 27 2024, 8:38 AM
Unknown Object (File)
Sep 22 2024, 7:20 PM
Unknown Object (File)
Sep 21 2024, 1:25 PM
Unknown Object (File)
Sep 20 2024, 11:25 AM
Subscribers

Details

Summary

Fixes the long uptake we saw on meta.phacility.com. I regressed this in D11795.

We make three calls to this method, but only one actually consumes the messages. The other two are just checking to see if there are any messages.

Only move the cursor up if we're actually going to process the messages.

Test Plan

Sort of tricky to test convincingly since it's inherently race-prone, but ran debug pulllocal and pushed update messages and saw it pick them up.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Only increment status message cursor if we're going to consume the message.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Feb 18 2015, 8:52 PM
This revision was automatically updated to reflect the committed changes.