-
Notifications
You must be signed in to change notification settings - Fork 7
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
NODE_RED_INSTANCE_NUMBER out of range with 1
#373
Comments
dkastl
added a commit
to dkastl/FIWARE-Big-Bang
that referenced
this issue
May 27, 2024
fisuda
added a commit
to fisuda/FIWARE-Big-Bang
that referenced
this issue
May 28, 2024
fisuda
added a commit
to fisuda/FIWARE-Big-Bang
that referenced
this issue
May 28, 2024
fisuda
added a commit
that referenced
this issue
May 28, 2024
Fix NODE_RED_INSTANCE_NUMBER value checking (#373)
Fixed by the PR #375. |
fisuda
pushed a commit
to fisuda/FIWARE-Big-Bang
that referenced
this issue
Jun 2, 2024
fisuda
added a commit
to fisuda/FIWARE-Big-Bang
that referenced
this issue
Jun 8, 2024
fisuda
pushed a commit
to fisuda/FIWARE-Big-Bang
that referenced
this issue
Jun 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Put an
x
in the boxes that applymake collect
command.Describe the bug
When I specify
an error is thrown like
However, if the setting is without explicit value
Then 1 instance is created as the default value claims: https://github.com/lets-fiware/FIWARE-Big-Bang/blob/main/config.sh#L314
Your system environment
This is independent from the system environment.
To Reproduce
See above.
Expected behavior
Probably specifying
1
forNODE_RED_INSTANCE_NUMBER
should not produce an error and create a single Nodered instance as the default does.Screenshots
If applicable, add screenshots to help explain your problem.
Server (please complete the following information):
Additional context
Add any other context about the problem here.
To resolve this issue, you need to provide complete information about your scenario.
The text was updated successfully, but these errors were encountered: