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

Unexpected token '<', "<html> <h"... is not valid JSON prevents ZWaveJS UI from starting #660

Closed
landolfi-us opened this issue Apr 20, 2024 · 1 comment
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@landolfi-us
Copy link

landolfi-us commented Apr 20, 2024

Problem/Motivation

I changed a backup cron specification and there may have been a message on the screen about an invalid format but the UI allowed me to save the invalid cron format.

Expected behavior

UI should refuse to save if the cron format is invalid.

Actual behavior

After the invalid specification was saved, a restart of ZwaveJS UI failed repeatedly with the error "Unexpected token '<', " <h"... is not valid JSON"

Steps to reproduce

Put a space at the beginning of a cron specificaton, e.g.: ' 22 10 * * *'

Proposed changes

Don't allow user to save backup settings that contain a cron specification with a space.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label May 21, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

1 participant