tensorflow / tensorflow/datasets
quest for datasets occur wrong
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 1.6k
- Avg merge
- 3h 54m
- Merged PRs (30d)
- 1
Description
Short description
my program try to get url https://www.googleapis.com/storage/v1/b/tfds-data/o/dataset_info%2Fcnn_dailymail%2Fplain_text%2F3.0.0?fields=size%2Cgeneration%2Cupdated,but failed
2020-08-20 08:41:35.983921: W tensorflow/core/platform/cloud/google_auth_provider.cc:178] All attempts to get a Google authentication bearer token failed, returning an empty token. Retrieving token from files failed with "Not found: Could not locate the credentials file.". Retrieving token from GCE failed with "Aborted: All 10 retry attempts failed. The last failure: Unavailable: Error executing an HTTP request: libcurl code 6 meaning 'Couldn't resolve host name', error details: Couldn't resolve host 'metadata'".
2020-08-20 08:42:37.024931: E tensorflow/core/platform/cloud/curl_http_request.cc:596] The transmission of request 0x5622d3c080e0 (URI: https://www.googleapis.com/storage/v1/b/tfds-data/o/dataset_info%2Fcnn_dailymail%2Fplain_text%2F3.0.0?fields=size%2Cgeneration%2Cupdated) has been stuck at 0 of 0 bytes for 61 seconds and will be aborted. CURL timing information: lookup time: 0.078541 (No error), connect time: 0 (No error), pre-transfer time: 0 (No error), start-transfer time: 0 (No error)
Contributor 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.
Research direction
Start by reproducing the dataset metadata request and read the warnings from tensorflow/core/platform/cloud/google_auth_provider.cc and tensorflow/core/platform/cloud/curl_http_request.cc. Check the reported missing credentials and failed metadata-host lookup, then determine whether the request completes successfully without the authentication and network errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python, tensorflow
- Domain
- cloud, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100