Datasets:
Download instances/observability-java-sdk-1982/problem_statement.md from CrossSWE/CrossSWE-Bench: direct link, hf CLI and curl.
- Browser
- Download file 1.2 kB
-
https://huggingface.co/datasets/CrossSWE/CrossSWE-Bench/resolve/main/instances/observability-java-sdk-1982/problem_statement.md
- Command line
-
hf download hf://datasets/CrossSWE/CrossSWE-Bench/instances/observability-java-sdk-1982/problem_statement.md
-
curl -L -o problem_statement.md https://huggingface.co/datasets/CrossSWE/CrossSWE-Bench/resolve/main/instances/observability-java-sdk-1982/problem_statement.md
Implement consistent domain-aware provider initialization in the OpenFeature Java and JavaScript SDKs.
A provider bound to a named OpenFeature domain is currently initialized without knowing which domain it serves. Providers that use the bound domain to scope persistent state can therefore collide with another domain's state, and a provider intended for one domain can be reused for multiple domains without being rejected.
Reproduction: register providers for named domains, initialize clients for those domains, and observe the initialization data received by each provider. Include a provider whose state must be isolated per domain, a provider used by more than one named domain, the default provider, and an existing provider implementation that supports only the legacy initialization behavior.
Expected behavior: providers receive the correct bound domain during initialization; domain-scoped providers cannot be bound to multiple domains; the default provider remains supported; and existing providers retain backward compatibility. Multi-provider behavior and the Java and JavaScript SDK semantics must remain consistent. Inspect both SDK repositories and ensure their relevant tests pass.