sequence-formats-1.12.1.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- haskell
- Domain
- build-system
Research direction
The failure is in src-executables/vcf2eigenstrat.hs at line 110 while building sequenceTools. Start by reading the code around the vcfToFreqSumEntry call and checking its return type against the value passed to yield. Run the reported Stack build to verify the error is resolved; the issue gives no test-file path.
Written by the indexing model from the issue text.
Description
@stschiff
Error: [S-7282]
Stack failed to execute the build plan.
While executing the build plan, Stack encountered the error:
[S-7011]
While building package sequenceTools-1.6.0.0 (scroll up to its section to see the error) using:
/home/curators/.stack/setup-exe-cache/x86_64-linux-tinfo6/Cabal-simple_w2MFVN35_3.14.2.0_ghc-9.12.4 --verbose=1 --builddir=.stack-work/dist/x86_64-linux-tinfo6/ghc-9.12.4 build lib:sequenceTools exe:genoStats exe:pileupCaller exe:vcf2eigenstrat test:sequenceToolsTests --ghc-options " -fdiagnostics-color=always"
Process exited with code: ExitFailure 1
Logs have been written to: /home/curators/work/unpack-dir/.stack-work/logs/sequenceTools-1.6.0.0.log
Preprocessing library for sequenceTools-1.6.0.0...
Building library for sequenceTools-1.6.0.0...
Preprocessing executable 'vcf2eigenstrat' for sequenceTools-1.6.0.0...
Building executable 'vcf2eigenstrat' for sequenceTools-1.6.0.0...
[1 of 1] Compiling Main
/home/curators/work/unpack-dir/unpacked/sequenceTools-1.6.0.0-9efb7f266292a58a990b571d03513b835b54d2844d0964bb1571e00b9ba90a4a/src-executables/vcf2eigenstrat.hs:110:11: error: [GHC-83865]
• Couldn't match expected type ‘FreqSumEntry’
with actual type ‘Maybe FreqSumEntry’
• In the first argument of ‘yield’, namely ‘fs’
In a stmt of a 'do' block: yield fs
In the expression:
do fs <- liftIO $ vcfToFreqSumEntry e
yield fs
|
110 | yield fs
| ^^
curator: Received ExitFailure 1 when running
Raw command: /usr/bin/stack --terminal build --test --test-suite-timeout=600 --no-rerun-tests --bench --no-run-benchmarks --haddock --no-interleaved-output --ghc-options -w --jobs=16
Run from: unpack-dir
- Dominant language
- Dockerfile
- Stars
- 550
- Forks
- 827
- Avg merge
- 23h 15m
- Merged PRs (30d)
- 7
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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 commercialhaskell/stackage
-
brick-3.0Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
commercialhaskell/stackage#8129 · 10 comments ·
-
time-manager-0.4.0Openfailure: bounds
Difficulty 1/5 Under an hour Newbie friendliness 72/100
commercialhaskell/stackage#8122 ·
-
dataframe-3.6.1.0Openfailure: bounds
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
commercialhaskell/stackage#8121 ·
-
unicode-data-0.9.0Openfailure: bounds
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
commercialhaskell/stackage#8118 · 1 comment ·
-
failure: bounds
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
commercialhaskell/stackage#8112 ·
All issues in commercialhaskell/stackage
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-telemetry/opentelemetry-go-compile-instrumentation#1512 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nasa/fprime#6225 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bioconda/bioconda-recipes#70401 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vitest-dev/vitest#11633 · 1 comment ·
Maintainers usually reply within 1 day