Instance state changes asynchronously in mock API #2167
Merged
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.
Instead of going straight to stopped (or started, or whatever it is) instances stop at an intermediate state (stopping, starting, etc.) immediately and only hit the target state after 1 second. Instance create does
creating (1s) -> starting (4s) -> running
.I've been meaning to do this for a while. It's neat because it lets us test the refresh button.
2024-04-18-instance-stopping-stopped.mp4