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

`DuplexTest.duplexWithAuthChallenge` flaky

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #9564 by @kamilkrzywanski — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, kotlin
Domain
networking, testing

Research direction

Start with DuplexTest.kt:549 and MockSocketHandler.kt:120, then run DuplexTest.duplexWithAuthChallenge on the testwindows runner to investigate the reported CANCEL reset. Done means the test no longer flakes there; linked pull request #9564 indicates related work has already been attempted.

Written by the indexing model from the issue text.

Description

tests windows

On 'testwindows' runner:

 DuplexTest[jvm] > duplexWithAuthChallenge()[jvm] FAILED
    java.util.concurrent.ExecutionException: okhttp3.internal.http2.StreamResetException: stream was reset: CANCEL
        at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
        at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:205)
        at okhttp3.internal.duplex.MockSocketHandler.awaitSuccess(MockSocketHandler.kt:120)
        at okhttp3.DuplexTest.duplexWithAuthChallenge(DuplexTest.kt:549)

        Caused by:
        okhttp3.internal.http2.StreamResetException: stream was reset: CANCEL
            at app//okhttp3.internal.http2.Http2Stream.checkOutNotClosed$okhttp(Http2Stream.kt:702)
            at app//okhttp3.internal.http2.Http2Stream$FramingSink.flush(Http2Stream.kt:631)
            at app//okio.RealBufferedSink.flush(RealBufferedSink.kt:270)
            at app//okhttp3.internal.duplex.MockSocketHandler.sendResponse$lambda$0$0(MockSocketHandler.kt:77)
            at app//okhttp3.internal.duplex.MockSocketHandler.serviceSocketTask$lambda$0(MockSocketHandler.kt:107)
            at [email protected]/java.util.concurrent.FutureTask.run(FutureTask.java:317)
            at app//okhttp3.internal.duplex.MockSocketHandler.handle(MockSocketHandler.kt:97)
            at app//mockwebserver3.MockWebServer$Http2SocketHandler.writeResponse(MockWebServer.kt:1224)
            at app//mockwebserver3.MockWebServer$Http2SocketHandler.onStream(MockWebServer.kt:1066)
            at app//okhttp3.internal.http2.Http2Connection$ReaderRunnable.headers$lambda$0$0(Http2Connection.kt:700)
            at app//okhttp3.internal.concurrent.TaskQueue$execute$1.runOnce(TaskQueue.kt:112)
            at app//okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
            at [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
            at [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
            at [email protected]/java.lang.Thread.run(Thread.java:1583)
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.