Fixes for Symfony 3.3 compatibility #19404
Merged
Conversation
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
|
Travis with |
|
Removed that stack trace check because that feels really silly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
It seems that some tests have broken with the release of Symfony 3.3.
The HTML error page containing the stack trace has changed, the corresponding test has been modified to correctly detect this error page.
Calling Symfony's
Request::setTrustedProxiesnow expects a second parameter containing a bit field ofRequest::HEADER_*([HttpFoundation] Add $trustedHeaderSet arg to Request::setTrustedProxies() - deprecate not setting it symfony/symfony#21830).Kind regards,
Jarno