Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Scheduler Chron table shows Invalid date #189

Closed
mvujica opened this issue Jul 20, 2024 · 2 comments
Closed

Scheduler Chron table shows Invalid date #189

mvujica opened this issue Jul 20, 2024 · 2 comments
Assignees
@jensrossbach
Labels
bug Something isn't working as expected
Milestone
Release 1.25

Comments

@mvujica
Copy link

mvujica commented Jul 20, 2024

Describe the bug
After update to node-red v4.0.2 from v3.x and node.js v20.15.1
Scheduler has error Invalid date for chron table schedule

To reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
Scheduler showing correct next date/time based on chron syntax

Screenshots
image
image

Context information
Please complete the following information.

  • Platform & OS: raspberry Pi Bullseye
  • node-red-contrib-chronos version: 1.25.3
  • Node-RED version: 4.0.2
  • Node.js version: 20.15.1

Additional information
Add any other information about the problem here.
@jensrossbach jensrossbach self-assigned this Jul 20, 2024
@jensrossbach jensrossbach added the bug Something isn't working as expected label Jul 20, 2024
@jensrossbach jensrossbach added this to the Release 1.25 milestone Jul 20, 2024
@jensrossbach
Copy link
Owner

Should be fixed with release 1.25.5.

@mvujica
Copy link
Author

mvujica commented Jul 20, 2024

Great, thx for such a great module and even better support. #191

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensrossbach jensrossbach

Labels
bug Something isn't working as expected
Projects
None yet
Milestone
Release 1.25
Development

No branches or pull requests
2 participants
@jensrossbach @mvujica