Skip to content

Conversation

@jbergler
Copy link

Prior to this change this script would fail if a controller has non
consecutive arrays because the script expects the array id to start at 0
and increment to the array count.

With this change we retrieve a list of all arrays per controller and
iterate through that way.

I believe this situation occurs when an array is deleted, in our
situation array 0 was removed leaving just 1 & 2

Fixes #26

Prior to this change this script would fail if a controller has non
consecutive arrays because the script expects the array id to start at 0
and increment to the array count.

With this change we retrieve a list of all arrays per controller and
iterate through that way.

I believe this situation occurs when an array is deleted, in our
situation array 0 was removed leaving just 1 & 2

Fixes eLvErDe#26
@ElCoyote27
Copy link
Contributor

ElCoyote27 commented Jan 20, 2016

Might be the same as issue #10

@jbergler jbergler closed this Feb 18, 2022
@jbergler jbergler deleted the master branch February 18, 2022 17:48
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

Successfully merging this pull request may close these issues.

megaclisas-status fails when arrays aren't consecutive

2 participants