refactor: clean up client-side keep-alive - #144
Merged
Merged
Conversation
EvanWiederspan
approved these changes
Sep 25, 2026
sethtroisi
approved these changes
Sep 25, 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
3 participants
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.
Why? With cl/982796273 rolled out to Prod, client-side
/keep-aliveping is effectively a no-op. Going forward, runtimes are automatically kept alive by the backend based on kernel activities and active connections.As a result, this PR cleans up the redundant
/keep-alivepings from Colab CLI. This also prevents other open source developers from replicating this retired mechanism.