We have discovered the cause of this issue and working on a fix to revert back to milliseconds. I will update as I know more.
Just curious what was the root cause and how come there isn’t any kind of regression testing in place to prevent this type of screw-ups?
Appreciate the quick response!!
There were unit tests in place and they all passed. In the old scheduler we were converting seconds to milliseconds at some point. This did not make it into the new scheduler, and has subsequently been added as a hotfix. Unit tests were also added to test against the proper values so that future updates will keep to the documented standard.
I adjusted my code reflect seconds vs milliseconds, and it appears to be working with seconds still. This would also explain why my bedroom lights were coming on until 3:00am the other day after tripping my alarm earlier in the evening. Someone owes my wife a big apology…,
Is there an ETA for this Hotfix?
I moved everything over to runIn() even though they don’t recommend runIn less than 1 minute. That part of the new scheduler seems to be fine. I don’t really want to break all of my rules again when delay switches back to milliseconds.
It’s been more than a week since this regression was discovered. I presume it’s fixed now, right?
That would be the person who set up the trigger, YOU…
That would be yesterday. Yep, that’s what they said.
At this point, it really doesn’t matter what they say. Expect nothing, and you will still be disappointed.
The problem was identified the same day it was reported. A fix was created and placed into our production repo 5 days ago. The next date on the release schedule is 4/6(tomorrow) and it is currently approved and ready for deployment sometime in the morning.
Can you confirm if this went into production today or not?
Apologies all, but we have delayed the release. I will get more information soon.
Was this fixed within the last day or two? My camera delay started acting funny so I tested it in IDE. It appears to be working on milliseconds again.
Yes, here are the notes for the release last week that contained a fix: