Skip to content

Add jupyter_server_documents to fix window OS file corruption due to …#1048

Merged
TRNWWZ merged 1 commit intoaws:release-4.0.0from
aws-jjyim:release-4.0.0
Feb 3, 2026
Merged

Add jupyter_server_documents to fix window OS file corruption due to …#1048
TRNWWZ merged 1 commit intoaws:release-4.0.0from
aws-jjyim:release-4.0.0

Conversation

@aws-jjyim
Copy link

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

  • Image update - Bug fix
  • Image update - New feature
  • Image update - Breaking change
  • SMD image build tool update
  • Documentation update

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.

  • Yes (Critical bug fix or security update)
  • No (New feature or non-critical change)
  • N/A (Not an image update)

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:

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works

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.

@aws-jjyim aws-jjyim requested a review from a team as a code owner February 3, 2026 23:07
@TRNWWZ TRNWWZ merged commit 71e4051 into aws:release-4.0.0 Feb 3, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants