aws / aws/amazon-sagemaker-examples

Bring Your Own DL Framework to Amazon Sagemaker with Model Server for Apache MXNet's (MMS) BYO container.ipynb failed CI

Open
#2,435 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
11k
Forks
7k
Avg merge
8h 29m
Merged PRs (30d)
8

Description

Link to the notebook:
https://github.com/aws/amazon-sagemaker-examples/blob/master/sagemaker-python-sdk/paddlepaddle_sentiment_analysis_byo_mms/Bring Your Own DL Framework to Amazon Sagemaker with Model Server for Apache MXNet's (MMS) BYO container.ipynb

Error:

---------------------------------------------------------------------------
Exception encountered at "In [11]":
---------------------------------------------------------------------------
CalledProcessError Traceback (most recent call last)
in
----> 1 get_ipython().run_cell_magic('sh', '', '\n# The name of our algorithm\nalgorithm_name=paddle-mms\n\naccount=$(aws sts get-caller-identity --query Account --output text)\n\n# Get the region defined in the current configuration (default to us-west-2 if none defined)\nregion=$(aws configure get region)\n# specifically setting to us-east-1 since during the pre-release period, we support only that region.\nregion=${region:-us-east-1}\n\necho "region is " $region\n\nfullname="${account}.dkr.ecr.${region}.amazonaws.com/${algorithm_name}:latest"\n\necho $fullname\n# If the repository doesn\'t exist in ECR, create it.\n\naws ecr describe-repositories --repository-names "${algorithm_name}" > /dev/null 2>&1\n

Contributor guide

Open the contributing guide

Research direction

Open the linked notebook at cell 11 and inspect the shell command that runs `aws ecr describe-repositories` for the `paddle-mms` repository. Reproduce the CI failure in the notebook's SageMaker/AWS environment, then verify that the cell completes successfully and the notebook passes its CI check.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, jupyter-notebook, shell
Domain
cloud, machine-learning
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.