EDDN: Bad date-time in outfitting and shipyard messages

[Athanasius]

This showed up in yesterday's logs:

2022-02-17 14:25:19,361 - ERROR - Gateway:274: Failed Validation "[<ValidationError: "'2022-02-17T14.25.19Z' is not a 'date-time'">]" (18979, "EDDLite", "2.0.0.0", "https://eddn.edcd.io/schemas/outfitting/2", "-") from <ip elided>
2022-02-17 14:42:17,984 - ERROR - Gateway:274: Failed Validation "[<ValidationError: "'2022-02-17T14.42.17Z' is not a 'date-time'">]" (475, "EDDLite", "2.0.0.0", "https://eddn.edcd.io/schemas/shipyard/2", "-") from <ip elided>
2022-02-17 15:06:19,401 - ERROR - Gateway:274: Failed Validation "[<ValidationError: "'2022-02-17T15.06.19Z' is not a 'date-time'">]" (10933, "EDDLite", "2.0.0.0", "https://eddn.edcd.io/schemas/outfitting/2", "-") from <ip elided>
2022-02-17 15:52:20,290 - ERROR - Gateway:274: Failed Validation "[<ValidationError: "'2022-02-17T15.52.20Z' is not a 'date-time'">]" (475, "EDDLite", "2.0.0.0", "https://eddn.edcd.io/schemas/shipyard/2", "-") from <ip elided>
2022-02-17 15:53:41,421 - ERROR - Gateway:274: Failed Validation "[<ValidationError: "'2022-02-17T15.53.41Z' is not a 'date-time'">]" (18979, "EDDLite", "2.0.0.0", "https://eddn.edcd.io/schemas/outfitting/2", "-") from <ip elided>

All the same user+ip. I assume it's objecting to the . hour/minute/second separators in the times.

[Eahlstan]

Robby and those separators are natural enemies.

Thanks for the report.

[Eahlstan]

Also this should have been already fixed by https://github.com/EDDiscovery/EliteDangerousCore/commit/f70b62f3848a6d2ae2590a1010b363659cf8e14b So it just needs a new release.

[robbyxp1]

Both EDD and EDDLite will get new releases in the next few weeks

[robbyxp1]

2.1 addresses this