chore(flagd): protobuf modules are only generated by a build
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system, ci-cd, testing
Research direction
Start by comparing the flagd provider setup with the flagd testkit's hatch_build_sync.py and the poe test flow. Trace how protoc generation currently depends on the hatch-protobuf build hook, then update the provider's test and build configuration and CONTRIBUTING.md to use the uv-era workflow. Done means tests generate importable protobuf modules before running, builds package the generated output, and the documented commands work without hatch.
Written by the indexing model from the issue text.
Description
The flagd provider's protobuf modules are generated only by the hatch-protobuf build hook, so nothing importable exists until a distribution is built.
Two consequences:
- CI runs
uv buildfor every package on every Python version, purely so this one package gets its generated modules. CONTRIBUTING.mdstill tells contributors to runhatch buildonce and to test withhatch test. Both predate the move to uv, andhatchis not a dependency of the repo any more, so following the instructions fails.
Generating code is a test input, not an artifact of the build (pypa/hatch#1824). The flagd testkit already handles this correctly: hatch_build_sync.py is an ordinary script, poe test runs it first, and the build hook only ships what it produced. The flagd provider should do the same for protoc.
- Dominant language
- Python
- Stars
- 27
- Forks
- 33
- Avg merge
- 11h 10m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from open-feature/python-sdk-contrib
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-feature/python-sdk-contrib#439 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-feature/python-sdk-contrib#433 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-feature/python-sdk-contrib#421 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
open-feature/python-sdk-contrib#417 · 1 comment ·
Maintainers usually reply within 1 day
-
Needs Triage question
Difficulty 4/5 3-5 days Newbie friendliness 48/100
open-feature/python-sdk-contrib#420 ·
Maintainers usually reply within 1 day
All issues in open-feature/python-sdk-contrib
Similar issues
-
New InternshipOpennew_internship
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
[BUG] Reports tab: "Unban" button tooltip shows raw `{{ip}}` placeholder instead of the IP addressOpenbug javascript ui
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bunkerity/bunkerweb#4001 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
adobe-fonts/source-serif#153 ·