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

Guzzle 7 Breaks Run-server Command #4655

Merged
merged 1 commit into from
Feb 17, 2023

Conversation

yyss8
Copy link
Contributor

@yyss8 yyss8 commented Feb 16, 2023

Motivation

Fixes #4656
We noticed that the run-server command constantly fails on our Travis build after upgrading to Drupal 10. After looking into the code, we found that the exceptions used in the checkUrl method is no longer respected in Guzzle 7 and causing a client error to be thrown when curl returns a 404 response .

image

The option was deprecated in Guzzle 6 and was removed in 7 according to this PR guzzle/guzzle#2464 (I don't see the option being marked deprecated anywhere)

Proposed changes

Switch to use the new option http_errors. The option was introduced in Guzzle 6, so it should be safe to use without changing anything in the composer.json file as Guzzle 6 was the minimum version required by Drupal 9.

Testing steps

  1. Set up a Drupal 10 site with BLT.
  2. Run blt tests:server:start -vvvv.

@danepowell danepowell added the Bug Something isn't working label Feb 17, 2023
@danepowell
Copy link
Contributor

Thanks for the PR!

@danepowell danepowell merged commit 16ba828 into acquia:main Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BLT-5202: Guzzle 7 Breaks Run-server Command
2 participants