sokrypton / sokrypton/ColabFold
Error: credential propagation was unsuccessful
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 2.9k
- Forks
- 747
- PR merge metrics
- No merged PRs in 30d
Description
MessageError Traceback (most recent call last)
/tmp/ipython-input-4-4085076963.py in <cell line: 0>()
38 from google.colab import auth
39 from oauth2client.client import GoogleCredentials
---> 40 auth.authenticate_user()
41 gauth = GoogleAuth()
42 gauth.credentials = GoogleCredentials.get_application_default()
2 frames
/usr/local/lib/python3.11/dist-packages/google/colab/auth.py in authenticate_user(clear_output, project_id)
258 if not _check_adc(_CredentialType.USER):
259 if use_auth_ephem:
--> 260 _message.blocking_request(
261 'request_auth',
262 request={'authType': 'auth_user_ephemeral'},
/usr/local/lib/python3.11/dist-packages/google/colab/_message.py in blocking_request(request_type, request, timeout_sec, parent)
174 request_type, request, parent=parent, expect_reply=True
175 )
--> 176 return read_reply_from_input(request_id, timeout_sec)
/usr/local/lib/python3.11/dist-packages/google/colab/_message.py in read_reply_from_input(message_id, timeout_sec)
101 ):
102 if 'error' in reply:
--> 103 raise MessageError(reply['error'])
104 return reply.get('data', None)
105
MessageError: Error: credential propagation was unsuccessful
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 failure at auth.authenticate_user() and inspect the shown google/colab/auth.py path, especially the call into _message.blocking_request(). Trace read_reply_from_input() in google/colab/_message.py and determine the conditions behind the credential propagation error; done means a verified cause and resolution for this traceback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100