Skip to content

Be Sure that Expander Zones are Marked as Such #62

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

Merged
merged 2 commits into from
Mar 9, 2025

Conversation

krkeegan
Copy link
Contributor

A zone can be initially created by an alphanumeric fault message.
When created this way, the expander attribute is not marked even
for expander zones.

However, when we receive an expander message, we should update
the zone attribute to be sure it is identified as an expander.

A zone can be initially created by an alphanumeric fault message.
When created this way, the expander attribute is not marked even
for expander zones.

However, when we receive an expander message, we should update
the zone attribute to be sure it is identified as an expander.
Copy link
Contributor

@edrikk edrikk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ajschmidt8
Given that you have commit access, I wanted to flag a few PRs/changes that I've been running cleanly for a couple of years. These changes will also enable updating/correcting the requirements.txt file.
I'll using this same "approve" comment across these items.

Copy link
Collaborator

@ajschmidt8 ajschmidt8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@ajschmidt8 ajschmidt8 merged commit 389607e into nutechsoftware:master Mar 9, 2025
1 check passed
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.

3 participants