dev: upgrade time circuits and add a flux capacitor (engine cycle monitor and pgmocktime) #2438
Conversation
This file contains 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
tony-tvu
approved these changes
Jun 14, 2022
| c.cycles[c.history[0]] = make(chan struct{}) | ||
| } | ||
|
|
||
| // startNextCycle marks the begining of the next engine cycle. |
|
Great work on this @mastercactapus and @KatieMSB 🧠 !! |
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.
Description:
This PR allows for the manipulation of space and time within the confines of a Postgres database.
It is now possible to move time forward, back, alter its speed, reverse its flow, and even go back to a specific point in the future. Engine cycles can be triggered using 2-stages for more efficient test runs (grab ID, trigger cycle, wait for ID).
This work also resolves a long-standing issue where the DB time code for smoketests changed the engine's perception of time, but failed to account for DEFAULT values in the tables. It is now possible to control things like alert-log timestamps to the millisecond, by freezing altering the passage of time.
/health/engine/cyclethat will return the next engine cycle ID/health/engineendpoint now accepts an optionalid=parameterpgmocktimetool was added that has both an API and CLI interface.task(...))Screenshots:
