Skip to content

feat(sagemaker-ai): add HyperPod debugging skills #169

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.

Sign up for GitHub

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
ssuday merged 2 commits into from
May 16, 2026

Merge branch 'main' into feat/hyperpod-debugging-skills

1dc2bd6
Select commit
Loading
Failed to load commit list.
Merged

feat(sagemaker-ai): add HyperPod debugging skills #169

Merge branch 'main' into feat/hyperpod-debugging-skills
1dc2bd6
Select commit
Loading
Failed to load commit list.
GitHub Advanced Security / Semgrep OSS succeeded May 16, 2026 in 3s

No new alerts in code changed by this pull request

View all branch alerts.

Annotations

Check notice on line 512 in plugins/sagemaker-ai/skills/hyperpod-slurm-debugger/scripts/slurm-diagnose.sh

See this annotation in the file changed.

Code scanning / Semgrep OSS

Semgrep Finding: bash.lang.correctness.unquoted-expansion.unquoted-variable-expansion-in-command Note

Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may use a variable that starts with an underscore e.g. $_X instead of $X, and semgrep will ignore it. If what you need is an array, consider using a proper bash array.

Check notice on line 512 in plugins/sagemaker-ai/skills/hyperpod-slurm-debugger/scripts/slurm-diagnose.sh

See this annotation in the file changed.

Code scanning / Semgrep OSS

Semgrep Finding: bash.lang.correctness.unquoted-expansion.unquoted-variable-expansion-in-command Note

Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may use a variable that starts with an underscore e.g. $_X instead of $X, and semgrep will ignore it. If what you need is an array, consider using a proper bash array.