googleapis / googleapis/google-cloud-cpp
Consider more strict checking of hash offsets
Open
api: storage
type: cleanup
- Dominant language
- C++
- Stars
- 659
- Forks
- 462
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 89
Description
I am not sure if the current code is a good idea, but I think it does not harm anything either.
Contributor guide
Research direction
The issue does not name any source file, test, or entry point; begin by locating the code that validates hash offsets in google-cloud-cpp. Clarify which offsets should be rejected and define tests that demonstrate the intended stricter behavior before making a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100