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

Better control over DNS lookups

Open
  • Is something wrong?
#438 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start by tracing the hostname-resolution path named in the issue: requests, urllib3, http.client, and socket. Compare the manual-resolution and IP-caching suggestions, then verify that the chosen approach provides controlled DNS timing without changing the REST client’s expected behavior.

Written by the indexing model from the issue text.

Description

feature

Currently, hostname resolution is done implicitly via requests -> urllib3 -> http.client -> socket. Connection timeout does not include the DNS timeout, so requests on a system with broken DNS take prohibitively long.

We could:

  • resolve the hostname manually, and gain control over timeout (suggestion here),
  • cache the IP address.
Dominant language
Python
Stars
63
Forks
44
Avg merge
2d 9h
Merged PRs (30d)
2

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 dwavesystems/dwave-cloud-client

All issues in dwavesystems/dwave-cloud-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.