Malformed Last Updated field

[luiscoms]

Expected Behavior

I set DATE_FORMAT config with following value

DATE_FORMAT = '%Y-%m-%d %H:%M:%S%z'

When I get resource, the _updated field does not show timezone

Actual Behavior

Result of get resource:

Fields on MongoDB

Environment

• Python version: 3.9.9

pip freeze -r requirements.txt
config-client==1.1.0
Eve==1.1.5
Eve-Elastic==7.2.1
eve-healthcheck==0.3.1
gunicorn==20.1.0
MarkupSafe==1.1.1
PyQueueManager==1.12.1
PyYAML==6.0

[luiscoms]

I've teste with Eve==2.0.2 too, same problem

[nicolaiarocci]

This is intended behavior, see this for the reasoning around it.

[luiscoms]

Ok, but Eve set UTC time here, does not make sense to remove tzinfo

[nicolaiarocci]

Hmm, that's the oplog push code, and in a conditional branch only executed when the last update info not available. Furthermore, it's set at UTC precisely because all last_updates must be timezone-less (see my link above.)

[luiscoms]

It was only an example code, here another example.
Why _create field, that is a Date field equals to _updated on MongoDB should be timezone-less?

[luiscoms]

A possible fix is

- updates[config.LAST_UPDATED] = datetime.utcnow().replace(microsecond=0)
+ updates[config.LAST_UPDATED] = datetime.utcnow().replace(microsecond=0, tzinfo=timezone.utc)

[nicolaiarocci]

Feel free to submit a PR, I'll be happy to review it.