Skip to content

Modifying existing patches and adding sagemaker integration patch #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 31, 2025

Conversation

saumitsAmazon
Copy link
Contributor

Description of changes:
Reorganised sagemaker patches as follows:

Testing: Created a Sagemaker distribution image using all sagemaker patches and created a code editor application on Sagemaker Studio using that.

Screenshot 2025-07-31 at 15 33 39

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@@ -11,6 +11,7 @@ common/remove-vsda.diff
common/embedded-api.diff
common/remove-disable-prompting-for-non-trusted-urls-option.diff
common/suppress-known-errors-script.diff
common/update-csp.diff
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is a common patch why it's not included in other series files? If there are concerns that it can impact other consumers we can keep it in the sagemaker folder for now (but let's create a task to move it to common and run appropriate tests).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving it under sagemaker patches path for now, will add based on testing outcome with other consumers.

});
}
+
+ if (env['EXTENSIONS_GALLERY']) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we document the support for this variable in the header of the patch?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, adding in a new revision

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think these changes are needed as we hook into the Localization service here:

Can you please check if the expected texts are displayed without a need to modify NLS files?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like we need this override. Localisation doesn't seem to replace the git extension configurations

Screenshot 2025-07-31 at 16 27 09

@saumitsAmazon saumitsAmazon merged commit ff4506d into main Jul 31, 2025
2 checks passed
@saumitsAmazon saumitsAmazon deleted the sagemaker-patch-integration branch July 31, 2025 16:25
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