aws / aws/amazon-sagemaker-examples
Identify Worker Accuracy.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/ground_truth_labeling_jobs/worker_labeling_efficiency/Identify Worker Accuracy.ipynb
Error:
---------------------------------------------------------------------------
Exception encountered at "In [13]":
---------------------------------------------------------------------------
NoSuchBucket Traceback (most recent call last)
in
----> 1 run_sanity_check(bucket)
2 write_worker_metrics(labeling_job_output_location, labeling_job_name, worker_metrics_output, golden_answers)
in run_sanity_check(bucket_name)
3 region = boto3.session.Session().region_name
4 s3 = boto3.client('s3')
----> 5 bucket_region = s3.get_bucket_location(Bucket=bucket_name)['LocationConstraint']
6 if bucket_region is None:
7 bucket_region = 'us-east-1'
/opt/conda/lib/python3.7/site-packages/botocore/client.py in _api_call(self, *args, **kwargs)
[...]
NoSuchBucket: An error occurred (NoSuchBucket) when calling the GetBucketLocation operation: The specified bucket does not exist
Contributor guide
Research direction
Open Identify Worker Accuracy.ipynb and start at In[13], where run_sanity_check(bucket) fails during GetBucketLocation. Check how the bucket value is supplied and reproduce the CI failure; done means the notebook no longer raises NoSuchBucket in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, jupyter-notebook, python
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100