Skip to content

fix(amazonq): fix for amazon q app initialization failure on sagemaker #7551

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 3 commits into from
Jun 25, 2025

Conversation

ashishrp-aws
Copy link
Contributor

Problem

GlibC paths are undefined and not available for SageMaker instances running in containers even thought their compute is Amazon linux 2. With no GlibC paths language server is not starting.

Solution

  • Skipping GlibC path check for sagemaker instances
  • Increasing checks for sagemaker instances

  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ashishrp-aws ashishrp-aws requested a review from a team as a code owner June 25, 2025 00:18
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@ashishrp-aws ashishrp-aws merged commit 1ab1ad2 into aws:master Jun 25, 2025
45 of 46 checks passed
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.

3 participants