warp: ambiguous modules in doctest #579

Closed
bergmark opened this Issue Aug 28, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@bergmark

The test suite is

The test-suite for this package has been disabled in stackage because of this issue. If a fix is published to hackage can you please ping me? You may not want to fix this since it's an issue with the combination of these packages, so feel free to close this if so.

Thanks!

Network/Wai/Handler/Warp/WithApplication.hs:12:1: error:
    Ambiguous interface for ‘Control.Concurrent.Async’:
      it was found in multiple packages: async-dejafu-0.1.2.2 async-2.1.0
@kazu-yamamoto

This comment has been minimized.

Show comment
Hide comment
@kazu-yamamoto

kazu-yamamoto Dec 6, 2016

Contributor

@snoyberg Do you think that we should fix it in Warp?
I think that async-dejafu should rename its module.

Contributor

kazu-yamamoto commented Dec 6, 2016

@snoyberg Do you think that we should fix it in Warp?
I think that async-dejafu should rename its module.

@snoyberg

This comment has been minimized.

Show comment
Hide comment
@snoyberg

snoyberg Dec 6, 2016

Member

I'd like that too. However, new idea...

@bergmark What do you think about adding a new setting to Stackage which marks packages as hidden, and tells stackage-curator to hide these packages after registering them, to avoid problems like this? I can imagine that metadata will also be useful for Stack down the road.

Member

snoyberg commented Dec 6, 2016

I'd like that too. However, new idea...

@bergmark What do you think about adding a new setting to Stackage which marks packages as hidden, and tells stackage-curator to hide these packages after registering them, to avoid problems like this? I can imagine that metadata will also be useful for Stack down the road.

@bergmark

This comment has been minimized.

Show comment
Hide comment
@bergmark

bergmark Dec 6, 2016

@snoyberg good idea! I think that will work out very nicely.

bergmark commented Dec 6, 2016

@snoyberg good idea! I think that will work out very nicely.

snoyberg added a commit to fpco/stackage-curator that referenced this issue Dec 11, 2016

snoyberg added a commit to commercialhaskell/stackage that referenced this issue Dec 11, 2016

@snoyberg

This comment has been minimized.

Show comment
Hide comment
@snoyberg

snoyberg Dec 11, 2016

Member

OK, I've made the relevant modification to both stackage-curator and build-constraints.yaml, so hopefully the tests will pass in the future. Should we close this and address any remaining issues among just the curator team?

Member

snoyberg commented Dec 11, 2016

OK, I've made the relevant modification to both stackage-curator and build-constraints.yaml, so hopefully the tests will pass in the future. Should we close this and address any remaining issues among just the curator team?

@bergmark

This comment has been minimized.

Show comment
Hide comment
@bergmark

bergmark Dec 11, 2016

Awesome, thanks! It Sounds good to me!

Awesome, thanks! It Sounds good to me!

@bergmark bergmark closed this Dec 11, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment