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

Java: close the internally created HttpClient in Bitpin.close()

Open
#31 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
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
backend

Research direction

Start by reading Config to see how it distinguishes an internally created java.net.http.HttpClient from one supplied by the user, then trace how Bitpin.close() disconnects the WebSocket. Update the close lifecycle so it closes only the internally created client. Done means closing an SDK client releases its internally created HttpClient while leaving a user supplied client open.

Written by the indexing model from the issue text.

Description

enhancement java

When no httpClient/restTransport is configured, Config builds a java.net.http.HttpClient. Since Java 21, HttpClient is AutoCloseable, and each one keeps a selector thread until it is garbage-collected. Bitpin.close() only disconnects the WebSocket.

For apps that create many short-lived clients, close() should also close the HttpClient the SDK created itself, but never one the user passed in.

Dominant language
Python
Stars
0
Forks
0
Avg merge
28m
Merged PRs (30d)
20

Getting set up

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 bitpin-dev/bitpin-sdk

All issues in bitpin-dev/bitpin-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.