Fix test suite failure edge case

This could *rarely* fail, because if it runs really close to the integer
timestamp ticking over (e.g. at sometime.999), we could end up with an
integer timestamp that ticks over and passes validation when it
shouldn't because the server processing code gets it at
(sometime+1).001.

Increase it by 1 to avoid the error.

Author: jagerman

tests/test_auth.py

@@ -274,13 +274,13 @@ def test_auth_malformed(client, db):
 
     # Bad timestamps
     r = client.get(
-        "/auth_test/whoami", headers=x_sogs(a, B, 'GET', '/auth_test/whoami', timestamp_off=86401)
+        "/auth_test/whoami", headers=x_sogs(a, B, 'GET', '/auth_test/whoami', timestamp_off=86402)
     )
     assert r.status_code == 425
     assert r.data == b'Invalid authentication: X-SOGS-Timestamp is too far from current time'
 
     r = client.get(
-        "/auth_test/whoami", headers=x_sogs(a, B, 'GET', '/auth_test/whoami', timestamp_off=-86401)
+        "/auth_test/whoami", headers=x_sogs(a, B, 'GET', '/auth_test/whoami', timestamp_off=-86402)
     )
     assert r.status_code == 425
     assert r.data == b'Invalid authentication: X-SOGS-Timestamp is too far from current time'