Page MenuHomePhabricator

Correct an issue with epoch timestamps in Conduit
ClosedPublic

Authored by epriestley on Jul 26 2016, 2:07 PM.
Tags
None
Referenced Files
F13132567: D16326.id39255.diff
Wed, May 1, 7:35 PM
Unknown Object (File)
Mon, Apr 29, 3:18 PM
Unknown Object (File)
Wed, Apr 24, 11:06 PM
Unknown Object (File)
Fri, Apr 19, 5:59 AM
Unknown Object (File)
Thu, Apr 11, 7:48 AM
Unknown Object (File)
Mar 29 2024, 9:18 PM
Unknown Object (File)
Mar 5 2024, 8:17 AM
Unknown Object (File)
Feb 10 2024, 4:33 PM
Subscribers
None

Details

Summary

Fixes T11375. Some validation code was mishandling raw epoch timestamps.

For numeric values larger than 29999999 (e.g., 2999-12-25, christmas 2999), assume the value is a timestamp.

Test Plan

Used maniphest.search to query for modifiedStart, got a better result set and saw the dateModified constraint in the query.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Correct an issue with epoch timestamps in Conduit.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Jul 26 2016, 3:45 PM
This revision was automatically updated to reflect the committed changes.