Hackbot-client raising httpx exceptions to its callers
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the Hackbot-client code path that ends in raise_for_status() and inspect how its public errors are handled. Define the client-facing error contract so callers do not need to depend on httpx.HTTPStatusError; done means transport exceptions are no longer exposed through this path.
Written by the indexing model from the issue text.
Description
We end in raise_for_status(), so the client's contract includes httpx.HTTPStatusError and httpx's version is part of its public API. Callers should not need to know the transport: a client library's job is to speak the domain, and this is the one place it doesn't.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Contributor guide
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 mozilla/bugbug
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100