Problem description
Meadow.OS has been enhanced to allow time in seconds to be greater than 0xffff (65545). The new maximum is 28 days - 1 second or 2,419,199 seconds. Please make this change in the appropriate code of Meadow.Foundation or Meadow.Core.
It was also noted that a date could be entered that had already passed. This will cause Meadow.OS to return an error where this condition is tested. It would be better to catch it in MC or MF.
Repo steps
Steps to reproduce the behavior:
Create a Meadow App using DateTime that is greater than 18 hours 15 minutes in the future and use it to call Device.PlatformOS.Sleep().
Create a Meadow App using DateTime where the time has already passed and use it to call Device.PlatformOS.Sleep().
Expected behavior
An error should be reported that when DateTime has already past.
An error should be reported when the DateTime is more than 2,419,199 second in the future.
Screenshots
If applicable, add screenshots to help explain your problem.
Meadow.Foundation (please complete the following information as best as you can):
NuGet package version: Don't know
Developer tools (please complete the following information as best as you can):
OS and version: Windows 11 Home v22H2
IDE and version: Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.5.4
Meadow extension for IDE version: Tools for Meadow v0.98.0
Meadow (please complete the following information as best as you can):
Most of these values can be found by running meadow device info using the Meadow CLI.
Meadow hardware version: F7v2
Meadow OS version: 0.9.9.23 (Built by me, Peter)
If they are different, please provide these versions as well.
Meadow Mono version: Same
Meadow coprocessor version: Not configured using default settings
Problem description Meadow.OS has been enhanced to allow time in seconds to be greater than 0xffff (65545). The new maximum is 28 days - 1 second or 2,419,199 seconds. Please make this change in the appropriate code of Meadow.Foundation or Meadow.Core. It was also noted that a date could be entered that had already passed. This will cause Meadow.OS to return an error where this condition is tested. It would be better to catch it in MC or MF.
Repo steps Steps to reproduce the behavior:
Expected behavior
Screenshots If applicable, add screenshots to help explain your problem.
Meadow.Foundation (please complete the following information as best as you can):
Developer tools (please complete the following information as best as you can):
Meadow (please complete the following information as best as you can): Most of these values can be found by running
meadow device info
using the Meadow CLI.