transparency-dev / transparency-dev/tessera
[Hammer] Support long-lived performance tests with private GCS bucket
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 238
- Forks
- 56
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 35
Description
Description
The existing hammer takes bearer token for read and write. However, the token can expire in 1 hour by default. The access token can be extended to 12 hours.
When the token is expired, the read access is revoked. Thus, all requests to the bucket including checkpoint and tiles will return 401.
W0301 01:13:15.008988 2604 hammer.go:102] get("https://storage.googleapis.com/bucket/checkpoint"): 401
Supporting gs://bucket_name/file_name scheme could be one of the solutions. Another workaround could be mounting the bucket to the local file system and use the file:// scheme.
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 with internal/hammer/hammer.go at the referenced lines 64-65 and inspect the request path around the 401 reported at line 102. Compare the proposed gs:// and file:// approaches for long-lived access to a private bucket, then define the supported behavior and verification needed to prevent reads from failing after the bearer token expires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100