Skip to content

[Deserialization] Do not assert on a missing witness if allowing errors #38869

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

Merged
merged 1 commit into from
Aug 13, 2021

Conversation

bnbarham
Copy link
Contributor

When allowing errors we may have serialized a requirement without a
witness, do not assert when deserializing.

Resolves rdar://81884767

@bnbarham bnbarham requested a review from xymus August 13, 2021 05:45
@bnbarham
Copy link
Contributor Author

This is just an assertion - it's already handled on the next line as the requirement as the requirement could have been optional/unavailable.

Another found from the stress tester.

When allowing errors we may have serialized a requirement without a
witness, do not assert when deserializing.

Resolves rdar://81884767
@bnbarham bnbarham force-pushed the empty-witness-assert branch from 8634f37 to 3afb498 Compare August 13, 2021 07:15
@swiftlang swiftlang deleted a comment from swift-ci Aug 13, 2021
@bnbarham
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@xymus xymus 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. Gotta love that stress tester!

@bnbarham bnbarham merged commit f1036c2 into main Aug 13, 2021
@bnbarham bnbarham deleted the empty-witness-assert branch August 13, 2021 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants