Add jupyter_server_documents to fix window OS file corruption due to …#1048
Merged
TRNWWZ merged 1 commit intoaws:release-4.0.0from Feb 3, 2026
Merged
Add jupyter_server_documents to fix window OS file corruption due to …#1048TRNWWZ merged 1 commit intoaws:release-4.0.0from
TRNWWZ merged 1 commit intoaws:release-4.0.0from
Conversation
f9850c6 to
b12c67c
Compare
TRNWWZ
approved these changes
Feb 3, 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.
Add jupyter_server_documents to fix window OS file corruption due to …
Description
Integrating jupyter_server_documents in order to fix a window OS file corruption issue mentioned in this sev2 ticket: https://t.corp.amazon.com/V1986525113/communication.
Type of Change
Release Information
Does this change need to be included in patch version releases? By default, any pull requests will only be added to the next SMD image minor version release once they are merged in template folder. Only critical bug fix or security update should be applied to new patch versions of existed image minor versions.
If yes, please explain why:
[Explain the criticality of this change and why it should be included in patch releases]
Impacted Customer was using SMD 2.x and this bug also exists in SMD 3.x. We want have a separate PR to include JSD in SMD 2.14 and 3.9.
How Has This Been Tested?
Tested with Manual installation of JSD in Space and also Custom Image from similar PR: #1030.
We will be merging this PR in to build the image to fully test with and will have follow up PRs if fixes are needed.
Checklist:
Test Screenshots (if applicable):
Please see PR: #1030.
Related Issues
https://t.corp.amazon.com/V1986525113/communication
Additional Notes
We will be merging this PR in to build the image to fully test with and will have follow up PRs if fixes are needed.