Cap the time_spent recorded per milestone to one hour

[jmkulwik]

We have had some cases where a student spends an extreme amount of time on a level between recording milestones. In some cases, a student will even record more time on a level than was physically possible (see "Example" below). In order to prevent such outliers, we are capping the time_spent per milestone to 1 hour.

Example

(Slack Conversation)[https://codedotorg.slack.com/archives/CA3KCSGTD/p1597952388014200]

On Aug 20th, 2020, time_spent recording had been enabled for ~24 hours. During that time, however, we had one student record approximately 19 days worth of time_spent on a single level. This was not possible and was likely due to an issue with the user's system clock.

Additionally, there is some worry that students who leave their browser open overnight or for multiple days will record extremely long time_spent without actually interacting with the site.

These two types of scenarios can erroneously cause large amounts of time_spent recorded for users.

Links

• LP-1542

Testing story

Reviewer Checklist:

• Tests provide adequate coverage
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[clareconstantine]

good call on the test!