status: stable output order of params with --verbose#84
Merged
Conversation
"halo status verbose" prints the resource parameters, such as below, within square braces. They are stored in a HashMap. iron2 (llnl/zpool) Running on iron2 [pool: iron2] iron2/mdt1 (llnl/lustre) Running on iron2 [dataset: iron2/mdt1; mountpoint: /mnt/lustre/lobster-MDT0001; type: mdt] The existing code iterates over the HashMap in a different order every time, so watch halo status --verbose produces constant change even when the resource states and parameters are not changing. Sort the parameters before printing them and their values to prevent this, making actual change easy to see.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
"halo status verbose" prints the resource parameters, such as below, within square braces. They are stored in a HashMap.
The existing code iterates over the HashMap in a different order every time, so
produces constant change even when the resource states and parameters are not changing.
Sort the parameters before printing them and their values to prevent this, making actual change easy to see.