'queue-monitor' app: add menu items to save plan history to local file #195
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.
I this PR three menu items were added to
queue-monitor
application (an application for controlling Queue Server) for saving plan history to a.txt
,.json
or.yaml
file. The application does not attempt to update the history from the server before saving, so it can be called even after the client is disconnected from the server. All items displayed in the Plan History widget are saved to the file. If the widgets shows no plans (e.g. before connecting to the server or after clearing the history), then no plans are going to be saved and the file will be empty.The
.isort
was (in part accidentally) run on the whole code base before changes were committed. To complete.isort
integration, the respective.isort
config file and Github workflow was added.Motivation and Context
Changes were requested by active users.
How Has This Been Tested?
Manually tested.