Space fast-follow feature implementation#370
Open
aws-brianxia wants to merge 1 commit intoaws:mainfrom
Open
Conversation
* feat: Implement elastic training cli arguments (aws#273) * feat: Implement elastic training cli arguments * Add elastic training unified config and unit test * Add graceful shutdown and scaling timeout to cli args * Revert "feat: Implement elastic training cli arguments (aws#273)" This reverts commit 18428ef2b1c0562bf51a9a4b4aa2914eed441259. * Remove space CLI error traceback --------- Co-authored-by: Sophia <yungwenh@amazon.com> Co-authored-by: Molly He <mollyhe@amazon.com> --- Implement port forwarding for space (aws#312) --- Implement MIG profile validation for spaces (aws#315)
mollyheamazon
approved these changes
Feb 13, 2026
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.
What's changing and why?
Space fast-follow feature implementation
Before/After UX
N/A
How was this change tested?
Tested in local Hyperpod clusters and passed all tests
Are unit tests added?
Yes
Are integration tests added?
Yes
Reviewer Guidelines
One of the following must be true: