commercialhaskell/stack

Кирилл Заборский

@qrilka_twitter

@magthe do you have any reproduction or it just happens sporadically?

Magnus Therning

@magthe

@qrilka_twitter I don't really have reproduction steps, but the code is available at: https://github.com/magthe/ci-test-hs/ (the branch Add Azure Pipelines)
Examples of CI builds at:

VM, pre-built binary: https://dev.azure.com/magthe/CI%20Test/_build/results?buildId=20 (I think one can reach that with a github account)
Building docker image (Build and deploy stage, if you look at earlier stages VM with pre-built binary worked): https://travis-ci.com/magthe/ci-test-hs/jobs/208730847
Successful build of docker image: https://cloud.drone.io/magthe/ci-test-hs/25/1/4 (again, I think a github account is sufficient)

Building image locally (docker build -t foo:0 .) first failed, then I followed the suggestion and added --verbose, then it succeeded. Howerver, the CI builds keep failing sporadically.

Magnus Therning

@magthe

Actually, it looks like all those links work without needing accounts at all :smiley:

Michael Snoyman

@snoyberg

Can you open an issue on it, and/or check if an issue is already opened, and ping me?

I think it might have to do with buffering of output, but I'm not sure

Magnus Therning

@magthe

Absolutely!

Magnus Therning

@magthe

@snoyberg here it is: commercialhaskell/stack#4888
Let me know if you need more information from me.

Dan Burton

@DanBurton

@snoyberg An odd thing with the display of this package.
https://www.stackage.org/lts-13.26/package/unordered-containers-0.2.10.0
Shows the "latest on hackage" as 0.2.9.0

Michael Snoyman

@snoyberg

I'll pass that along @DanBurton

Michael Snoyman

@snoyberg

@DanBurton I think I've fixed it with this commit, it still needs to deploy fpco/stackage-server@07f3ef2

Michael Snoyman

@snoyberg

Woohoo, it's fixed now https://www.stackage.org/lts-13.26/package/unordered-containers-0.2.10.0

Dan Burton

@DanBurton

Ah, good ol' "comparing numbers lexicographically", where "10" < "9". Good catch!

Michael Snoyman

@snoyberg

Thanks :)

I had fun explaining that one to a non-technical family member

Magnus Therning

@magthe

I see there's a release 2.1.1.1 available on Hackage, but no corresponding tag on GitHub. Is that just an oversight?

Кирилл Заборский

@qrilka_twitter

@magthe quoting Manny Borsboom "Yeah, I suppose I could make a tag but it's not a real version of Stack -- it exists only to remove a file from the tarball on Hackage."

Magnus Therning

@magthe

Ah, OK... I'm not sure where I would have been able to find that information without asking though.

Кирилл Заборский

@qrilka_twitter

yes, there is such a problem with it

Michael Snoyman

@snoyberg

If anyone is running into the "mirrors.json is expired" issue, please see this issue for explanation and workaround:

commercialhaskell/stack#4928

Also, please feel free to weigh in with a vote on that issue.

Magnus Therning

@magthe

Ouch... the workaround is OK for local builds, but a bit tedious when trying to get CI builds going again :/

Michael Snoyman

@snoyberg

You can put that config in your stack.yaml as well if you want

As you can tell, I'm in favor of disabling the export checks

Magnus Therning

@magthe

Ah, yes, I just realized it can go into the project's stack.yaml too.

Magnus Therning

@magthe

It is pretty obvious you are in favour of that yes :grin:
I think that, no matter what the security concerns are and how valid they are, it's a bad situation to be in, relying on upstream to keep that JSON file up-to-date when they apparently have let it expire a few times by now.

Aditya Manthramurthy

@donatello

I am trying to formulate a container based workflow to build a haskell project. The idea is to share a container with all project deps (ghc, stack, libs) with other developers, so that when they build the project, only the project's files need to be built and not the deps. This workflow was possible in the 1.9.x stack version, but it is breaking in the 2.x version (all files in the project are built every time stack build is launched within the build container). Is there a workaround to let stack pick up pre-compiled dependencies from the container and still have the project build incrementally?

Dan Burton

@DanBurton

I believe the same workflow should still be possible, with the caveat that a cache built with stack 1.9 is not usable by stack 2.x; the cache must be built by stack 2.x if it is to be used by stack 2.x.

Aditya Manthramurthy

@donatello

Maybe I've been using a hacky approach - the package cache in my build image is in /root/.stack (when I build the image with either stack version). The (multi-package) project directory is mounted into the container at /project - when I run stack 1.9 in this directory, stack keeps its work in /project/.stack-work and is able to build incrementally (i.e. when i change some source files in the project and rebuild, only the changed files and packages that depend on it are re-built). In 2.x perhaps because the sqlite db is in /root/.stack, every build rebuilds all the packages in /project.

Is there a better way @DanBurton ?

Dan Burton

@DanBurton

I'm not familiar enough with the pantry-related changes to give a good answer to that. Perhaps @snoyberg can help? ^

Michael Snoyman

@snoyberg

I'd recommend testing with the latest on stable, we made some changes that affect caching a bit, check out the ChangeLog

gbaz

@gbaz

Ay. Richard Eisenberg wanted to see if there were any stack-specific issues to be discussed with regards to the "provenance qualified package imports" proposal: ghc-proposals/ghc-proposals#115

My sense is that this is all generally build-tool agnostic stuff that's prior to that phase, but it is indeed good to double check

Cary Robbins

@carymrobbins

This bug brings much sadness into my life - commercialhaskell/stack#4786

Compiler thinks a type is different depending on where it is referenced

Are there any workarounds in the meantime? Maybe even some tips as to how someone could submit a patch to fix it?

Michael Snoyman

@snoyberg

@carymrobbins any chance that there are cyclic dependencies at play here?

Cary Robbins

@carymrobbins

@snoyberg I think technically no, there shouldn't be, unless this introduces one -

A stack project with two packages core and testlib

testlib:lib depends on core:lib

core:test depends on testlib:lib

I see core:test as a separate target from core:lib, so the arrow should look like

core:lib -> testlib:lib -> core:test

But maybe something in stack considers both core:lib and core:test the same target in some way?

hovind

@hovind

Hi, folks! stack build puts things in .stack-work/install/x86_64-linux-tinfo6, does anyone know how I can generate the arch-vendor-abi triplet (in this case x86_64-linux-tinfo6) in a portable manner?