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

Fix warnings in tests. #193

Merged
merged 4 commits into from
Mar 19, 2018
Merged

Conversation

normanmaurer
Copy link
Member

Motivation:

When running swift test two warnings were printed.

Modifications:

  • Signal that we want to ignore the return value
  • Use boolean test in the while loop

Result:

Cleaner build

Motivation:

When running swift test two warnings were printed.

Modifications:

- Signal that we want to ignore the return value
- Use boolean test in the while loop

Result:

Cleaner build
@normanmaurer normanmaurer requested review from weissi and Lukasa March 19, 2018 13:03
@normanmaurer normanmaurer added this to the 1.3.0 milestone Mar 19, 2018
@normanmaurer normanmaurer added the 🔨 semver/patch No public API change. label Mar 19, 2018
Copy link
Member

@weissi weissi left a comment

Choose a reason for hiding this comment

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

👍

@normanmaurer normanmaurer merged commit b6dbaa5 into apple:master Mar 19, 2018
@normanmaurer normanmaurer deleted the test_warnings branch March 19, 2018 18:36
weissi pushed a commit to weissi/swift-nio that referenced this pull request Jun 13, 2020
…rotocol (apple#193)

Motivation:

Applications might want to support H2 (when available) and HTTP1 (as a fallback).
The application logic should not change between the two versions of the protocol
and the code to configure support for both the protocols is boilerplate and can
be provided as an helper function.

Modifications:

This PR adds an helper function to configure HTTP1 or H2 pipelines according to
the protocol negotiated by the TLS handler.

Result:

Applications that need to support clients using both HTTP1 and H2 can
configure their channels by calling `configureCommonHTTPServerPipeline`,
which should reduce the boilerplate they have to write.

Co-Authored-By: Cory Benfield <lukasa@apple.com>
weissi pushed a commit to weissi/swift-nio that referenced this pull request Feb 3, 2024
# Motivation
Currently the `QuiescingHelper` is crashing on a precondition if you call shutdown when it already was shutdown. However, that can totally happen and we should support it.

# Modification
Refactor the `QuiescingHelper` to exhaustively switch over its state in every method. Furthermore, I added a few more test cases to test realistic scenarios.

# Result
We are now reliable checking our state and making sure to allow most transitions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants