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.

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

[BUG] #5

Closed
ChristoffelG opened this issue Jul 7, 2023 · 9 comments
Closed

[BUG] #5

ChristoffelG opened this issue Jul 7, 2023 · 9 comments

Comments

@ChristoffelG
Copy link

Describe the bug
Seemingly internal TypeError

To Reproduce
Steps to reproduce the behavior:
The node was working fine and it started giving issues without me touching it again.
I stopped referencing it and its still giving errors

Expected behavior
Output time to next LS and duration

Software (please complete the following information):

  • node-red-contrib-eskomsepush version: 0.0.12
@ChristoffelG
Copy link
Author

It gives this error: "TypeError: dates.stages[EskomSePushInfo.calc.stage] is not iterable"

@HSPilot2008
Copy link

Having the same issue

It gives this error: "TypeError: dates.stages[EskomSePushInfo.calc.stage] is not iterable"

@dirkjanfaber
Copy link
Owner

Can I get some info on the area are you using?

@ChristoffelG
Copy link
Author

It looks like the issue happens when you leave it on test for a while. When I disable test for a few minutes the error stops.

@HSPilot2008
Copy link

It looks like the issue happens when you leave it on test for a while. When I disable test for a few minutes the error stops.

My test option is disabled for 30 mins now. Still the same

@ChristoffelG
Copy link
Author

Can I get some info on the area are you using?

Im in erasmusrand

@HSPilot2008
Copy link

Can I get some info on the area are you using?

jhbcitypower2-8-sundowner

@dirkjanfaber
Copy link
Owner

Thanks. I am able to reproduce the issue.

dirkjanfaber added a commit that referenced this issue Jul 12, 2023
The wrong schedule was taken (array starts counting at 0, the stage at 1). This
off by one resulted in not being able to find a schedule during stage 8
load shedding. (issue #5)
In case of an event, the start end and time where not stored in the
calculated object, resulting in an "invalid date" status.
@dirkjanfaber
Copy link
Owner

Created a new release, fixing this. Should be updatable from the palette manager shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants