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

CMRI usernames in wrong table column #4616

Closed
JLang1951 opened this Issue Dec 23, 2017 · 5 comments

Comments

Projects
None yet
4 participants
@JLang1951
Copy link

JLang1951 commented Dec 23, 2017

I installed 4.10 the other day and I like all of the new features for monitoring and configuring CMRI nodes but I have noticed one problem that I want to report. When I pull up the list asignments for my SIMNI nodes the user names for the I/O's show up in the comments column and not the user names column. Not a big deal but thought that I would point it out. Here is my panel if someone wants to look at it.
JDL_NYC_Panel.zip
NCE Simulated
CMRI Simulated.

Thanks John L.

@rhwood rhwood changed the title New CMRI features in 4.10 CMRI usernames in wrong table column Dec 23, 2017

@rhwood rhwood added the Bug label Dec 23, 2017

@CCatania01

This comment has been minimized.

Copy link
Contributor

CCatania01 commented Dec 23, 2017

The list assignments from the main C/MRI menu display is incorrect. Listing bit assignments for a node from the Node Configuration Manager, displays the information correctly.
Will be corrected in a 4.11.x release.

@KenC57

This comment has been minimized.

Copy link
Contributor

KenC57 commented Dec 23, 2017

@CCatania01

This comment has been minimized.

Copy link
Contributor

CCatania01 commented Dec 24, 2017

@CCatania01

This comment has been minimized.

Copy link
Contributor

CCatania01 commented Jan 26, 2018

Corrected. PR #4824

@CCatania01

This comment has been minimized.

Copy link
Contributor

CCatania01 commented Feb 3, 2018

Would JLang1951 please review, and close.
Thanks,
Chuck Catania

@JLang1951 JLang1951 closed this Feb 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment