Fix: Move checkTerminalActivity to server side #181
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.
Issue #, if available:
Description of changes:
Problem: The
sagemaker-idle-extensionchecks if there is an active terminal session by checking for the existence of/dev/ptsentries in the file system. However, when the user closes the Code Editor browser tab, thesagemaker-idle-extensionis deactivated, so even if an active terminal process is still running, the idle shutdown countdown starts.Solution: We move the
checkTerminalActivityfunction to the/api/idlehandler on the code server side, so that it runs even when the browser tab is closed. The/api/idleendpoint is called by the SageMaker Studio service on a 1-minute interval to determine whether the Code Editor instance is idle or not.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.