Article date_time validation seems to be about one hour ahead

[cognivore]

While importing from RSS, if the time is set to approximately current (for example it's 22:00 UTC, and date: is getting set to 21:57), dev.to deployment won't accept the post.

A significant reduction in time should be applied for the post to be posted. For example, 20:57 UTC shall work.

Expected behaviour: dev.to deployment accepts the post.

Post in question: https://dev.to/doma/parser-combinators-in-rust-1f2e

A 10 second summary: https://www.youtube.com/watch?v=4ddiTSWtwB8

To Reproduce

1. Go to dev.to/settings/extensions
2. Enter RSS feed like https://doma.dev/atom.xml
3. Click Save Feed Settings
4. Choose a post to publish, for example "Parser combinators in Rust"
5. Click "Edit"
6. Change time to current minus three minutes, make sure to keep the time zone intact
7. Click "Save"
8. Get confusing error actually advertising wrong time format!
9. Change the time to current minus one hour and three minutes, make sure to keep the time zone intact
10. Click "Save"
11. Now the post saves, even though both attempts were valid

Expected behavior

Expected behaviour: dev.to deployment accepts the post when we click "Save" the first time.

Screenshots

https://www.youtube.com/watch?v=4ddiTSWtwB8

Desktop (please complete the following information):

• OS, version: Linux, Windows
• Browser, version: Firefox

Smartphone (please complete the following information):

• Device: NAN
• OS, version: NAN
• Browser, version: NAN

Additional context

Ditto

[github-actions]

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.

To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

[gogi2811]

I would like to take this issue up.

[citizen428]

Thanks for volunteering @gogi2811, I assigned you the issue now.

[cognivore]

After some tinkering, I came to think it's a user error which is due to daylight saving time.
Using correct time zone and letting backend figure it out fixes it.
In my case, posting from London, replacing UTC with BST works.