Bug: FlagStore does not interrupt watcher thread on shutdown
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with FlagStore.java at shutdown and the streamPayloads.take() call, then read InProcessResolver.java where stateWatcher is managed. Trace how shutdown reaches the watcher and check whether it exits; done means the streamer thread no longer hangs after shutdown.
Written by the indexing model from the issue text.
Description
After calling FlagStore::shutdown, the streamer thread was not stopped.
This thread hangs at final QueuePayload payload = streamPayloads.take();.
This could be fixed by stopping the stateWatcher from within InProcessResolver.
java-sdk-contrib version 0.14.0
- 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
-
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 2 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
-
[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 82/100
WalletConnect/walletconnect-monorepo#7389 · 1 comment ·
-
help wanted testing
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
elhajahmadj/offline-emergency-library#108 ·
Maintainers usually reply within 1 day
-
Add documentation for Transaction-bound OTP generationPossibly taken @radimtrojek-rgb claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
wultra/powerauth-nextstep#86 ·
-
API `/api/dataverses/{identifier}/dataset/linkingDataverses?alreadyLinking=true` returns at most 1 collectionPossibly taken A pull request linked to this issue is open or already merged. OpenType: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
OpenLineage/OpenLineage#5138 ·
Maintainers usually reply within 2 days