Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`ThreadInterruptTest.forciblyStopDispatcher` flaky

Open
  • Is something wrong?
#9,706 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
kotlin
Domain
testing

Research direction

Start with ThreadInterruptTest.forciblyStopDispatcher in ThreadInterruptTest.kt, around line 198, and read the surrounding test and dispatcher behavior. Run the JVM test to reproduce the flaky assertion; done means it reliably observes the expected cancellation message rather than "interrupted".

Written by the indexing model from the issue text.

Description

tests 
 ThreadInterruptTest[jvm] > forciblyStopDispatcher()[jvm] FAILED
    org.opentest4j.AssertionFailedError: expected to start with:<"canceled due to"> but was:<"interrupted">
        at app//okhttp3.internal.http.ThreadInterruptTest.forciblyStopDispatcher(ThreadInterruptTest.kt:198)
Dominant language
Kotlin
Stars
47.1k
Forks
9.3k
Avg merge
18h 18m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lysine-dev/okhttp

All issues in lysine-dev/okhttp

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.