Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Berdir’s picture

Status: Active » Needs review
FileSize
2.36 KB

Another easy conversion, haven't run the tests yet.

Status: Needs review » Needs work

The last submitted patch, update-guzzle-1862538-1.patch, failed testing.

Berdir’s picture

Status: Needs work » Needs review
FileSize
1.41 KB

This should pass the tests and is more like the original code.

rbayliss’s picture

Looks good to me.

YesCT’s picture

#3: update-guzzle-1862538-3.patch queued for re-testing.

Sutharsan’s picture

Status: Needs review » Reviewed & tested by the community

I've got nothing to add. It's RTBC to me.

Berdir’s picture

Status: Reviewed & tested by the community » Needs review

Needs to be re-rolled to use the exception handling pattern from the standardize issue. Which should probably wait until that is commited.

Otherwise, this will result in an uncatched exception bubbling up all the way if e.g. the network or d.o is down.

YesCT’s picture

here is the standardize issue @Berdir suggests going in first: #1875792: Standardize Guzzle exception handling

Berdir’s picture

Re-roll. Looks better now :)

ParisLiakos’s picture

Status: Needs review » Needs work

just one thing

+++ b/core/modules/update/update.fetch.incundefined
@@ -149,12 +151,13 @@ function _update_process_fetch_task($project) {
+    } catch (RequestException $exception) {

should be in a newline after closing }

Berdir’s picture

Status: Needs work » Needs review
FileSize
1.21 KB

There you go. Was too lazy for an interdiff ;)

ParisLiakos’s picture

Status: Needs review » Reviewed & tested by the community

ready to fly, thanks:)

twistor’s picture

And what about BadResponseException?

Berdir’s picture

That's a subclass of RequestException. We only need to differentiate if we want to log different errors otherwise re-act differently on them. I think the default getMessage() of either exception is fine for this.

twistor’s picture

Ahh, right.

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Committed 28f278b and pushed to 8.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.