[go-feature-flag] Should remote evaluation emit events and fail init on an unreachable relay proxy?
Maintainers usually reply within 1 day
@thomaspoignant is already working on this.
Since Oct 20, 2026.
Assessment
This issue has not been assessed yet.
Description
Running the provider TCK against the Java GO Feature Flag provider (#1947) showed the two evaluation types behaving differently in three places. I'm not sure whether that is intended, so asking before proposing anything.
In remote mode, RemoteEvaluator passes initialize straight to OfrepProvider and adds nothing on top. As a result:
- A relay proxy that can't be reached does not fail init. A provider pointed at a dead port reaches
READY. In-process fails, because its init fetches/v1/flag/configuration. - No
PROVIDER_CONFIGURATION_CHANGED. Nothing polls, so a flag change only shows up on the next evaluation. - No
PROVIDER_STALE. An outage only shows up as per-evaluation errors. In-process goes stale after 3 failed polls (STALE_AFTER_CONSECUTIVE_FAILURES).
This matches OFREP: the server-provider guideline has no initialisation step, no polling and no events, and the OFREP API has no health endpoint. So remote mode does what OFREP asks. The question is only whether GO Feature Flag wants more than that, using its own relay-proxy endpoints:
- Should remote mode watch for changes, emitting
PROVIDER_CONFIGURATION_CHANGEDandPROVIDER_STALE? In-process already polls/v1/flag/configurationwith the ETag, and/v1/flag/changeor the SSE stream may be lighter. Or is that too much for a mode people pick so they don't sync configuration? - Should init probe the relay proxy, e.g.
GET /health, so a misconfigured endpoint fails fast instead of reachingREADY?
None of this is a spec violation. The TCK records these capabilities as not attempted in remote mode, not as defects. Whichever way this goes, I'll update the adoption to match.
The Go provider's remote mode behaves the same way: its init never contacts the relay proxy and nothing polls (go-sdk-contrib#1053).
Related: #1850 (OFREP codeDefaultFlag → FLAG_NOT_FOUND) is a separate issue that also affects remote mode.
- Dominant language
- Java
- Stars
- 50
- Forks
- 87
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 53
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/java-sdk-contrib
-
Bug: FlagStore does not interrupt watcher thread on shutdownPossibly taken @lbarrosby claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-feature/java-sdk-contrib#1966 ·
Maintainers usually reply within 1 day
-
test(flagd): drop the per-scenario /stop in e2e teardown once the testbed includes flagd-testbed#396Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-feature/java-sdk-contrib#1891 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-feature/java-sdk-contrib#1861 ·
Maintainers usually reply within 1 day
-
fix!: opentelemetry-semconv-incubating bump renames feature_flag.provider_name attributePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-feature/java-sdk-contrib#1843 ·
Maintainers usually reply within 1 day
-
[ConfigCat] Evaluation errors are returned as a successful default with no error codePossibly taken @RaphaelFakhri claimed this 3 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
open-feature/java-sdk-contrib#1963 ·
Maintainers usually reply within 1 day
All issues in open-feature/java-sdk-contrib
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ahmedmmordi/store-app#8 ·
-
jhipster heroku fails on heroku git:remote when reusing an existing app outside a git repositoryOpenarea: triage theme: undefined
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jhipster/generator-jhipster#36018 ·
Maintainers usually reply within 1 day
-
component/zeebe kind/feature scope/broker
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day