aws / aws/amazon-sagemaker-examples
r_in_sagemaker_processing.ipynb failed CI
- 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/r_examples/r_in_sagemaker_processing/r_in_sagemaker_processing.ipynb
Error:
---------------------------------------------------------------------------
Exception encountered at "In [8]":
---------------------------------------------------------------------------
UnexpectedStatusException Traceback (most recent call last)
in
15 ProcessingOutput(output_name='images',
16 destination='{}/images'.format(output_destination),
---> 17 source='/opt/ml/processing/images')])
18
19 preprocessing_job_description = script_processor.jobs[-1].describe()
/opt/conda/lib/python3.7/site-packages/sagemaker/processing.py in ru
[...]
UnexpectedStatusException: Error for Processing job R-in-Processing-11-00-02-37: Failed. Reason: ClientError: API error (404): manifest for 521695447989.dkr.ecr.us-west-2.amazonaws.com/r-in-sagemaker-processing:latest not found: manifest unknown: Requested image not found
Contributor guide
Research direction
Open r_examples/r_in_sagemaker_processing/r_in_sagemaker_processing.ipynb and start at cell In [8], where the SageMaker processing job fails. Trace how the r-in-sagemaker-processing image is referenced and built or published, then rerun the notebook's CI path; done means the referenced image is available and the processing job no longer fails with the missing-manifest error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, jupyter-notebook, r
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100