Timestamp for PersonImage

[VirginiaDooley]

This work

• changes the PersonImage to a TimeStampedModel
• add a migration with default timestamps for created and updated which takes data from last queued image to populate existing PersonImage instances.
• renders the timestamp in the template to help users decide if a photo should be updated (very recent photos may not need updating at all)
  

These changes will also lay the groundwork for a more straightforward approach to refactoring #2386

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1207697305640851

[VirginiaDooley]

BST problems? I tried this again with freeze_time and also changed the migration update and created default to datetime.now(timezone.utc).isoformat() but got the same error.

[symroe]

Is this working now? CI seems ok?

[VirginiaDooley]

No, I don't think so - it's a mismatch in the time.

[symroe]

I've pushed a commit that fixes this, but I'm a little confused as to why we're not getting the right timezone back from pi.modified. In my understanding, the model should store the timezone and return local time, but maybe that's not how it works.

[sentry]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ AttributeError: 'NoneType' object has no attribute 'updated' people.migrations.0047_alter_personimage_option... View Issue

_{Did you find this useful? React with a 👍 or 👎}