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

test that we tolerate out-of-band data #1197

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

weissi
Copy link
Member

@weissi weissi commented Oct 29, 2019

Motivation:

We don't support OOB data but we should make sure that nothing breaks if
OOB arrives.

Modifications:

Add a test that makes sure we tolerate OOB data.

Result:

More test coverage.

@weissi weissi requested review from Lukasa and glbrntt October 29, 2019 11:29
Copy link
Contributor

@glbrntt glbrntt left a comment

Choose a reason for hiding this comment

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

Looks good minus the prb failing!

public static func sendto(descriptor: CInt,
pointer: UnsafeRawPointer,
size: size_t,
flags: CInt,
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn’t this an API breaking change? Or am I missing something?

How come we have public methods on an internal enum?

@Lukasa Lukasa added the patch-version-bump-only For PRs that when merged will only cause a bump of the patch version, ie. 1.0.x -> 1.0.(x+1) label Oct 29, 2019
@Lukasa Lukasa added this to the 2.10.0 milestone Oct 29, 2019
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.

Fine modulo @glbrntt’s feedback.

@weissi weissi added 🔼 needs-minor-version-bump For PRs that when merged cause a bump of the minor version, ie. 1.x.0 -> 1.(x+1).0 and removed patch-version-bump-only For PRs that when merged will only cause a bump of the patch version, ie. 1.0.x -> 1.0.(x+1) labels Oct 29, 2019
@glbrntt
Copy link
Contributor

glbrntt commented Oct 30, 2019

New test failed on 5.1... 👎

@weissi weissi modified the milestones: 2.10.0, 2.11.0 Nov 7, 2019
Motivation:

We don't support OOB data but we should make sure that nothing breaks if
OOB arrives.

Modifications:

Add a test that makes sure we tolerate OOB data.

Result:

More test coverage.
@Lukasa Lukasa modified the milestones: 2.11.0, 2.12.0 Dec 9, 2019
@weissi weissi modified the milestones: 2.12.0, 2.13.0 Dec 20, 2019
@weissi weissi modified the milestones: 2.13.0, 2.14.0 Jan 26, 2020
@Lukasa Lukasa modified the milestones: 2.14.0, 2.15.0 Feb 14, 2020
@weissi weissi removed this from the 2.15.0 milestone Mar 18, 2020
@Lukasa Lukasa changed the base branch from master to main September 24, 2020 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔼 needs-minor-version-bump For PRs that when merged cause a bump of the minor version, ie. 1.x.0 -> 1.(x+1).0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants