network-control

Open
#8,174 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
haskell
Domain
build-system

Research direction

Start by reading how Stackage records package bounds for snapshots and inspect the package metadata for network-control, http2, http3, and quic. The issue says network-control 0.2.0 falls outside the listed constraints and that an upper bound will be placed; determine which package bounds need updating and check the relevant Stackage validation. Done when the affected constraints are handled and the package set accepts the result.

Written by the indexing model from the issue text.

Description

network-control-0.2.0 (changelog) (Kazu Yamamoto [email protected] @kazu-yamamoto) is out of bounds for:

  • http2-5.4.9 (>=0.1 && < 0.2). Kazu Yamamoto [email protected] @kazu-yamamoto, Stackage upper bounds. Used by: library
  • http3-0.1.5 (>=0.1.7 && < 0.2). Andreas Ländle @alaendle, Stackage upper bounds. Used by: library
  • quic-0.3.4 (>=0.1.5 && < 0.2). Kazu Yamamoto [email protected] @kazu-yamamoto, Stackage upper bounds. Used by: library

Will place an upper bound on network-control for now

Dominant language
Dockerfile
Stars
550
Forks
831
Avg merge
18h 10m
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from commercialhaskell/stackage

All issues in commercialhaskell/stackage

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.