[ConfigCat] Evaluation errors are returned as a successful default with no error code
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- backend-api-design
Research direction
Start with ConfigCatProvider's getEvaluation method, which the issue identifies as ignoring EvaluationDetails.getError(), and reproduce the cases using the module tests' local features.json override. Done means missing flags return FLAG_NOT_FOUND with reason ERROR, and other evaluation errors return GENERAL with the ConfigCat error message.
Written by the indexing model from the issue text.
Description
Observed behavior
When ConfigCat cannot evaluate a flag, ConfigCatProvider returns the caller's default value with no errorCode, no errorMessage and no reason. Error hooks do not run, and the evaluation looks successful.
This affects at least these cases:
- The flag key does not exist in the config.
- The flag type does not match the requested type, for example
getIntegerDetailson a string setting.
ConfigCat itself detects both errors and reports them in EvaluationDetails.getError(), but getEvaluation ignores that field.
Expected behavior
A missing flag resolves with errorCode=FLAG_NOT_FOUND and reason=ERROR. Other ConfigCat evaluation errors resolve with an error code (GENERAL) and the ConfigCat error message.
Steps to reproduce
Use the provider with the local features.json override from the module tests:
FlagEvaluationDetails<String> details = client.getStringDetails("non-existing", "fallback_str");
// value=fallback_str, reason=null, errorCode=null, errorMessage=null
ConfigCat logs [1001] Failed to evaluate setting 'non-existing' (the key was not found in config JSON), but the OpenFeature result reports no error.
Version: dev.openfeature.contrib.providers:configcat 0.2.1 (current main), configcat-java-client 9.4.4.
- 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
-
[go-feature-flag] Should remote evaluation emit events and fail init on an unreachable relay proxy?Possibly taken @thomaspoignant claimed this 16 days ago. Open
open-feature/java-sdk-contrib#1948 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in open-feature/java-sdk-contrib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
scylladb/scylla-cdc-source-connector#402 ·
Maintainers usually reply within 1 day
-
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