geyanggang opened a new issue, #10315:
URL: https://github.com/apache/gravitino/issues/10315

   ### Version
   
   main branch
   
   ### Describe what's wrong
   
   The GCS credential integration tests (test_gvfs_with_gcs_credential.py) fail 
when using
   temporary OAuth2 tokens from Gravitino Server. The gcsfs library (upgraded 
from 2024.3.1
   to 2026.2.0) no longer accepts raw token strings and requires a 
google.auth.credentials.Credentials
   object instead.
   
   All 19 tests in TestGvfsWithGCSCredential fail, while TestGvfsWithGCS (using 
service account
   file) passes successfully.
   
   
   
   ### Error message and/or stacktrace
   
   File "gcsfs/credentials.py", line 59, in _get_creds_from_raw_token
   raise ValueError("Provided token is either not valid, or expired.")
   ValueError: Provided token is either not valid, or expired.
   
   ERROR: test_rmdir 
(tests.integration.test_gvfs_with_gcs_credential.TestGvfsWithGCSCredential)
   Traceback (most recent call last):
   File "gravitino/filesystem/gvfs_storage_handler.py", line 408, in 
get_filesystem_with_expiration
   self.get_filesystem(token=credential.token(), **kwargs)
   ...
   File "gcsfs/credentials.py", line 59, in _get_creds_from_raw_token
   raise ValueError("Provided token is either not valid, or expired.")
   
   ### How to reproduce
   
   cd gravitino-internal/clients/client-python
   python3 -m venv venv
   source venv/bin/activate
   pip install .
   pip install -r requirements-dev.txt
   
   export 
GCS_SERVICE_ACCOUNT_JSON_PATH_FOR_CREDENTIAL="/path/to/service-account.json"
   export GCS_BUCKET_NAME_FOR_CREDENTIAL="your-bucket-name"
   
   python -m unittest tests.integration.test_gvfs_with_gcs_credential -v
   
   ### Additional context
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to