Setting credential repository for a host doesn't work, uses 100% CPU, and is super wide
Setting credential repository for a host doesn't work, uses 100% CPU, and is super wide
Description:
There's 3 issues here, but I'm doing a single post since they deal with the same thing.
- When editing a host and setting the credentials for a credential repository item, it doesn't work. It shows it selected, but after saving you when trying to connect to the host you get prompted for credentials. Editing the host again shows the credentials still selected. Note that this only seems to be an issue when configuring the entry from RDM Linux. Hosts that were setup this way in RDM Windows will open correctly on RDM Linux
- To add to this, when the drop down for selecting the credential is open (or trying to open), CPU usage spikes and the RDM process uses 100% of a single thread (doesn't seem to be multithreaded, so the application is using all the CPU it can)
- The edit host popup is now pretty wide, which no way to reduce it.
Steps to reproduce:
- Right click a host and select "Edit Entry" (CPU goes to 100% while waiting for the popup to open). When it opens, notice the width (it's wider than my 1920x1080 screen)
- Set Credentials to "Credential repository"
- Click the drop down to select which credential to use from the repository (note CPU goes to 100% while the drop down menu is opening, and while this drop down menu is open)
- Select an entry that contains credentials for this host
- Click save
- Note that in the dashboard it does not show a username/password for this host
- Attempt to connect to the host
- Note a popup asking to select a credential entry
- Select the same entry you configured in step 4 and notice you can connect to the server
- Edit the host entry again, notice that the credential repository item is still selected and is correct.
All Comments (10)
Hi,
I'm working on this issue and was wondering, how many connection would you estimate is loaded in the combobox?
I couldn't reproduce the 100% cpu usage but I probably have nowhere near the same amount of data you have.
Jonathan Lafontaine
Looks like 4818
Yeah ok, I simple combobox might not cut it.
Are you able to open the combobox in window without any problems or rely on another window to select your credential?
Jonathan Lafontaine
I'm not sure I understand the question. Here's a screenshot of the host editor when credential repository is selected (not that I have 2 monitors and RDM is maximized in the background. I can open the drop down and the 100% CPU core exists as it's loading the list into the combobox it seems. Once it's loaded, CPU drops and I can search through and select a credential (although as my original post, it doesn't seem to use that. Also, the list is very long). The ... button on the right appears to do nothing, but IIRC from windows RDM, I'm assuming that will eventually lead to a search box for filtering?
That's right, the "..." button opens a new window in RDM Windows that allows selecting a credential with filtering and search options.
I've fixed the issue where selecting a credential on Linux didn't actually allow the connection to use it to connect.
I'm now working on usability issues.
Jonathan Lafontaine
Sweet, thanks!
The "..." should work and behave much like it's Windows/Mac counterpart in the next release.
I don't think there's anything I can do to prevent 100% cpu usage when opening the combobox but using the Credential Selection window should make the experience much better.
I've also moved stuff around and limited the length the combobox can take. That, however, means some credential's name might be too long.
The ellipse is a the beginning of the string so hopefully, people will still be able to know which entry is which.
Jonathan Lafontaine
I think the 100% CPU issue is probably low priority. We've got a ton of entries and it seems like it's better than it was before. Once the ellipse is in, we'll just use that.
Is there a target date you can share for the next release?
Somewhere in the next two weeks is what we are aiming for right now.
Jonathan Lafontaine
This is fixed (as we had discussed) in 2020.2.4.0