tolerate unknown fields#62
Merged
Merged
Conversation
anmonteiro
approved these changes
Dec 27, 2021
Owner
|
Thanks! |
Contributor
Author
|
@anmonteiro The nix build failed. I saw something similar before with cachix action being outdated, so I pushed a commit with updated cachix version to at least rule that out. |
Contributor
Author
|
I'm not seeing mismatched hashes for menhir. I'm assuming that I tried updating the overlays in |
Owner
|
I updated it recently, you need to use |
Owner
|
@joprice don't worry about CI for now, I'll fix it soon. |
Contributor
Author
|
It at least builds and |
anmonteiro
force-pushed
the
tolerateUnknownFields
branch
from
d8f8c4d to
5883125
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
strictmode was not disabled forapi_gateway_request_identity, so some new fields likecognitoAmrare causing body parsing to fail.