Cleanup: restore the interrupt flag in the API client and health checker
Maintainers usually reply within 1 day
@Rishankgupta08 is already working on this.
Since Nov 14, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- testing-qa
Research direction
Start with the three named spots: ApiAuth.java around line 117, ApiClient.java around line 142, and ApiHealthChecker.java around line 70, all under src/main/java/com/seleniumboot. In each, find the catch block that swallows InterruptedException and add Thread.currentThread().interrupt() while keeping the existing handling. Done when those three spots restore the flag, behaviour is otherwise unchanged, and mvn test passes.
Written by the indexing model from the issue text.
Description
Part of the cleanup cycle from #251. SonarCloud rule java:S2142 flags these spots.
These places catch InterruptedException (often inside catch (Exception e)) and carry on without restoring the thread's interrupt flag. Anything further up that checks Thread.interrupted() (a parallel runner shutting down, a timeout) never sees the interrupt.
Where (line numbers as of master 2a07bba):
src/main/java/com/seleniumboot/client/ApiAuth.java: line 117src/main/java/com/seleniumboot/client/ApiClient.java: line 142src/main/java/com/seleniumboot/precondition/ApiHealthChecker.java: line 70
Fix: restore the flag and keep the existing behaviour. For a combined catch, split it out:
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
// then the same handling the old catch did (log / wrap / return)
} catch (Exception e) {
...
}
Done when: the listed spots restore the interrupt flag, the behaviour is otherwise unchanged, and mvn test passes. Keep this PR to this package. SonarCloud reruns on the PR.
- Dominant language
- Java
- Stars
- 12
- Forks
- 6
- Avg merge
- 10h
- Merged PRs (30d)
- 76
Getting set up
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 seleniumboot/selenium-boot
-
Cleanup: restore the interrupt flag in AiFailureAnalyzerPossibly taken @Rishankgupta08 claimed this today. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seleniumboot/selenium-boot#258 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
seleniumboot/selenium-boot#256 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
seleniumboot/selenium-boot#255 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 42/100
seleniumboot/selenium-boot#259 ·
Maintainers usually reply within 1 day
-
SuggestionsOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
seleniumboot/selenium-boot#251 · 1 comment ·
Maintainers usually reply within 1 day
All issues in seleniumboot/selenium-boot
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
johanhaleby/occurrent#1505 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FasterXML/jackson-databind#6443 ·
Maintainers usually reply within 1 day
-
Docs: 2 broken linksOpen
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
finos/fluxnova-bpm-platform#387 ·
Maintainers usually reply within 4 days