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

Add special serialization handling for nullable ValueTuples #4713

Merged
merged 3 commits into from
May 27, 2020
Merged

Conversation

russcam
Copy link
Contributor

@russcam russcam commented May 26, 2020

This PR adds special serialization handling for nullable ValueTuples. Specialized handling is required as without, a nullable ValueTuple type ends up falling into CustomDynamicObjectResolver inside of
NestFormatterResolver, which will build a dynamic formatter using MetaType et.al, which enumerates interfaces and can cause a CLR error when calling System.Runtime.CompilerServices.ITuple.get_Length().

Fixes #4703

This commit adds special serialization handling for nullable ValueTuples.
Specialized handling is required as without, a nullable ValueTuple type
ends up falling into CustomDyanmicObjectResolver inside of
NestFormatterResolver, which will build a dynamic formatter using
MetaType et.al, which enumerates interfaces and can cause a
CLR error when calling `at System.Runtime.CompilerServices.ITuple.get_Length()`.

Fixes #4703
@russcam
Copy link
Contributor Author

russcam commented May 27, 2020

rebased on top of master

@russcam russcam merged commit 55cc44c into master May 27, 2020
@russcam russcam deleted the fix/4703 branch May 27, 2020 03:31
github-actions bot pushed a commit that referenced this pull request May 27, 2020
This commit adds special serialization handling for nullable ValueTuples.
Specialized handling is required as without, a nullable ValueTuple type
ends up falling into CustomDyanmicObjectResolver inside of
NestFormatterResolver, which will build a dynamic formatter using
MetaType et.al, which enumerates interfaces and can cause a
CLR error when calling `at System.Runtime.CompilerServices.ITuple.get_Length()`.

Fixes #4703
github-actions bot pushed a commit that referenced this pull request May 27, 2020
This commit adds special serialization handling for nullable ValueTuples.
Specialized handling is required as without, a nullable ValueTuple type
ends up falling into CustomDyanmicObjectResolver inside of
NestFormatterResolver, which will build a dynamic formatter using
MetaType et.al, which enumerates interfaces and can cause a
CLR error when calling `at System.Runtime.CompilerServices.ITuple.get_Length()`.

Fixes #4703
russcam added a commit that referenced this pull request May 27, 2020
…4715)

This commit adds special serialization handling for nullable ValueTuples.
Specialized handling is required as without, a nullable ValueTuple type
ends up falling into CustomDyanmicObjectResolver inside of
NestFormatterResolver, which will build a dynamic formatter using
MetaType et.al, which enumerates interfaces and can cause a
CLR error when calling `at System.Runtime.CompilerServices.ITuple.get_Length()`.

Fixes #4703

Co-authored-by: Russ Cam <russ.cam@elastic.co>
russcam added a commit that referenced this pull request May 27, 2020
…4716)

This commit adds special serialization handling for nullable ValueTuples.
Specialized handling is required as without, a nullable ValueTuple type
ends up falling into CustomDyanmicObjectResolver inside of
NestFormatterResolver, which will build a dynamic formatter using
MetaType et.al, which enumerates interfaces and can cause a
CLR error when calling `at System.Runtime.CompilerServices.ITuple.get_Length()`.

Fixes #4703

Co-authored-by: Russ Cam <russ.cam@elastic.co>
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.

SIGSEGV when indexing nullable value tuple with value
1 participant