Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to build in Stackage Nightly #37

Open
juhp opened this issue Jan 28, 2025 · 1 comment
Open

failed to build in Stackage Nightly #37

juhp opened this issue Jan 28, 2025 · 1 comment

Comments

@juhp
Copy link

juhp commented Jan 28, 2025

       [2 of 3] Compiling SequenceTools.Utils                     
       /home/curators/work/unpack-dir/unpacked/sequenceTools-1.5.3.1-54e9f0959a741bf603bcc485603f256e26a21f561f025ac7d572cd6a858bcc84/src/SequenceTools/Utils.hs:46:32: error: [GHC-83865]
           • Couldn't match type ‘Int’ with ‘(Int, Int)’       
             Expected: Maybe (Int, Int) -> GenoEntry                                                                                
               Actual: Maybe Int -> GenoEntry                     
           • In the first argument of ‘map’, namely               
               ‘(dosageToEigenstratGeno diploidizeCall)’                                                                            
             In the second argument of ‘(.)’, namely                                                                                
               ‘map (dosageToEigenstratGeno diploidizeCall)’                                                                        
             In the first argument of ‘($)’, namely                                                                                 
               ‘fromList . map (dosageToEigenstratGeno diploidizeCall)’                                           
          |                                                       
       46 |         geno = fromList . map (dosageToEigenstratGeno diploidizeCall) $ calls                                           
          |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
juhp added a commit to commercialhaskell/stackage that referenced this issue Jan 28, 2025
@stschiff
Copy link
Owner

damn, you guys are fast. There was literally only 1 or 2 days or so where this bug could have occurred, as I have updated a dependent library earlier. It should be resolved with the latest hackage commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants