This repository has been archived by the owner on Mar 7, 2019. It is now read-only.
Future drift #6
Open
Future drift #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please advise what's happening with these failing tests - I ran the branch through Travis and all appeared healthy. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During Django app development I occasionally have to manually trigger my windows client to NTP synchronise following a 'request in the future' response from the development raven service. Having spoken to other django developers within UCam this seems to be the case for others too.
The process to manually synchronise is quite frustrating (Windows), so I would like to propose an extra, optional, config variable UCAMWEBAUTH_NTPDRIFT which allows the admin to set the number of milliseconds it will allow a response to be appear in the 'future'.