No longer builds (on stackage) with network-3.2.11.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- haskell
- Domain
- networking
Research direction
The error comes from src/Network/HaskellNet/SMTP.hs around line 188, where getHostName is ambiguous between the imports from Network.BSD (line 80) and Network.Socket (line 81). Start by reading those two import lines and the call site, then check which getHostName the code is meant to use. Done means the package compiles against network-3.2.11.0 without the ambiguity error.
Written by the indexing model from the issue text.
Description
/home/curators/work/unpack-dir/unpacked/HaskellNet-0.6.2-6c69d25f62ce5ecb49b87546d052b67fa8e548f7c161dd87274c696c563f9314/src/Network/HaskellNet/SMTP.hs:188:33: error: [GHC-87543]
Ambiguous occurrence ‘getHostName’.
It could refer to
either ‘Network.BSD.getHostName’,
imported from ‘Network.BSD’ at src/Network/HaskellNet/SMTP.hs:80:21-31,
or ‘Network.Socket.getHostName’,
imported from ‘Network.Socket’ at src/Network/HaskellNet/SMTP.hs:81:1-21
(and originally defined in ‘network-3.2.11.0:Network.Socket.Posix.HostName’).
|
188 | senderHost <- T.pack <$> getHostName
@lemol, will disable the package for now
- Dominant language
- Haskell
- Stars
- 92
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
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
- 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 qnikst/HaskellNet
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
qnikst/HaskellNet#107 · 1 comment ·
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
qnikst/HaskellNet#84 ·
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
qnikst/HaskellNet#80 ·
-
feature help needed
Difficulty 5/5 Over a week Newbie friendliness 35/100
qnikst/HaskellNet#77 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
qnikst/HaskellNet#68 ·
All issues in qnikst/HaskellNet
Similar issues
-
validateXmirOptions error message is missing the word 'option'Possibly taken @opusstudiohq-max claimed this 1 day ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
objectionary/phino#2256 ·
Maintainers usually reply within 1 day
-
30-minutes algorithm any-language codewars dart easy elixir hackerrank hacktoberfest haskell help wanted interview-prep julia leetcode lua open-source r scala students zig
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Huerte/algo-solutions-python#163 ·
Maintainers usually reply within 1 day
-
subsystem: saw-core type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
GaloisInc/saw-script#3516 ·
Maintainers usually reply within 1 day
-
linear
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MercuryTechnologies/ghciwatch#466 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
yesodweb/wai#1163 · 1 reaction ·
Maintainers usually reply within 1 day