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

docker cleanup #90

Merged
merged 2 commits into from
Mar 5, 2018
Merged

docker cleanup #90

merged 2 commits into from
Mar 5, 2018

Conversation

tomerd
Copy link
Member

@tomerd tomerd commented Mar 3, 2018

Motivation:

repository currently contains two seperate docker definitions that are confusing to users

Modifications:

  • remove Dockerfile.xenial so we have a canonical docker file for CI and developer testing
  • point docker compose to canonical docker file
  • define docker compose services for unit and integration tests. and make "test" service run both
  • update readme

Result:

users are less confused about docker setup

Motivation:

repository currently contains two seperate docker definitions that are confusing to users

Modifications:

* remove Dockerfile.xenial so we have a canonical docker file for CI and developer testing
* point docker compose to canonical docker file
* define docker compose services for unit and integration tests. and make "test" service run both
* update readme

Result:

users are less confused about docker setup
@Lukasa
Copy link
Contributor

Lukasa commented Mar 3, 2018

Why do we need to remove Dockerfile.xenial?

@tomerd
Copy link
Member Author

tomerd commented Mar 3, 2018

@Lukasa to make docker compose based testing identical to our CI. there is an argument to be made to add tests for both versions, but until we do i prefer to avoid the confusion this can (and did) cause , and allow running integration tests via docker compose which was not possible in the existing version

@normanmaurer
Copy link
Member

@tomerd @Lukasa I am fine with the removal as long as we can test everything with 14.04 without any problems :)

@tomerd
Copy link
Member Author

tomerd commented Mar 3, 2018

yup, that’s what we use in CI

Copy link
Contributor

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, please rebase. 😁

@normanmaurer
Copy link
Member

@tomerd please rebase and merge.

@Lukasa Lukasa added the semver/minor Adds new public API. label Mar 5, 2018
@Lukasa Lukasa merged commit 142ee43 into apple:master Mar 5, 2018
@normanmaurer normanmaurer added this to the 1.1.0 milestone Mar 5, 2018
weissi pushed a commit to weissi/swift-nio that referenced this pull request Jun 13, 2020
Motivation:

RFC 7540 requires that HTTP/2 pseudo-headers must be first in a HTTP/2
header block, and must occur before any regular headers. We should enforce
that requirement.

Modifications:

- Added checking that pseudo-headers are first in a header block.

Result:

Better RFC 7540 validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/minor Adds new public API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants