Repository navigation
feat(plugin:dashboard): keep the step durations for the ETA in one file per step - #778
Merged
Merged
Conversation
…le per step Parallel runs, e.g. several ansible-navigator sessions, no longer need a lock or a read-merge-write cycle: each step file is replaced atomically, the last run wins. Durations are loaded per play, so a run picks up what parallel runs learned meanwhile. The 90-day expiry is dropped.
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.
Parallel runs, e.g. several ansible-navigator sessions, no longer need a lock or a read-merge-write cycle: each step file is replaced atomically, the last run wins. Durations are loaded per play, so a run picks up what parallel runs learned meanwhile. The 90-day expiry is dropped.
The old
durations.jsonanddurations.lockin/var/tmp/lfops/dashboardare no longer read and can be removed by hand.