Michael Scherer 7118984b64 Fix traceback when the creation date is exactly at 0 ms ...

nb found that one user was blocking the cronjob from running.
After looking closely, the problem was the creation date is
similar to 2017-02-01 09:10:20+00:00 , so without any dot,
as it was created at the exact microsecond the second started.

The usual format is 2017-02-01 09:10:20.012+00:00, where
split('.') work fine.

Since the traceback stop the whole cronjob, this prevented all
people whose login was after m from having the lifecycle badges.

2021-03-19 08:14:02 +00:00

..

files

Fix traceback when the creation date is exactly at 0 ms

2021-03-19 08:14:02 +00:00

tasks

Add a name, and do not spam root@ uselessly

2020-10-01 22:38:23 +02:00

templates

…