[Bug]: editing schedule updates with non-zero seconds
Closed this issue · 1 comments
aaronchongth commented
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
OS and version
Ubuntu 22.04
Open-RMF installation type
Source build
Other Open-RMF installation methods
No response
Open-RMF version or commit hash
main, deploy/hammer
ROS distribution
Humble
ROS installation type
Docker
Other ROS installation methods
No response
Package or library, if applicable
No response
Description of the bug
- Creating a new schedule will ensure the
start_fromtime has 0 seconds and milliseconds, to ensure when the scheduler is triggered on the minute, it will consider the task for execution as intended - Editing a prior schedule will currently save the seconds information into
start_from, hence making schedules not able to run if the scheduler is checking before the seconds mark
Steps to reproduce the bug
- Create schedule
- Edit schedule and monitor entry changes in the DB
- Task will not run if the seconds recorded is non zero
Expected behavior
No response
Actual behavior
No response
Additional information or screenshots
No response
aaronchongth commented
this has not been observed anymore