Add logs for error from helm install
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reading issue 72 and tracing the launcher's helm install operation. Identify the existing failure path and determine where its error output should be surfaced; done means failed helm installs emit logs through the HyperPod CLI.
Written by the indexing model from the issue text.
Description
Follow up from issue: https://github.com/aws/sagemaker-hyperpod-cli/issues/72
When the helm install operation fails in the launcher, no logs are emitted by the HyperPod CLI.
- Dominant language
- Python
- Stars
- 41
- Forks
- 95
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/sagemaker-hyperpod-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
aws/sagemaker-hyperpod-cli#348 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aws/sagemaker-hyperpod-cli#314 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
aws/sagemaker-hyperpod-cli#431 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
aws/sagemaker-hyperpod-cli#384 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
aws/sagemaker-hyperpod-cli#353 ·
All issues in aws/sagemaker-hyperpod-cli
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#14043 ·
Maintainers usually reply within 1 day
-
netbox status: needs triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
netbox-community/netbox#23376 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
githubnext/gh-aw-workshop#4455 ·
Maintainers usually reply within 1 day
-
Triage 🩺
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day