Testing existence of bucket incorrect
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 181
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
GCSFileSystem().exists(<bucket>) does not work (anymore) on buckets in 'other' projects - it returns False even though service account has full access to the project (account is project owner in all).
However using <bucket>/<file> does work and returns True.
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 at the GCSFileSystem().exists() entry point and reproduce the behavior with a bucket in another Google Cloud project, comparing bucket-only and bucket/file paths. Trace the bucket lookup and permission handling; done means exists() returns True when the service account can access that bucket, with regression coverage for cross-project buckets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, google-cloud, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100