Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
update.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Dec 2012 at 00:50 UTC
Updated:
29 Jul 2014 at 21:38 UTC
Jump to comment: Most recent file
Comments
Comment #1
berdirAnother easy conversion, haven't run the tests yet.
Comment #3
berdirThis should pass the tests and is more like the original code.
Comment #4
rbayliss commentedLooks good to me.
Comment #5
yesct commented#3: update-guzzle-1862538-3.patch queued for re-testing.
Comment #6
sutharsan commentedI've got nothing to add. It's RTBC to me.
Comment #7
berdirNeeds 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.
Comment #8
yesct commentedhere is the standardize issue @Berdir suggests going in first: #1875792: Standardize Guzzle exception handling
Comment #9
berdirRe-roll. Looks better now :)
Comment #10
ParisLiakos commentedjust one thing
should be in a newline after closing }
Comment #11
berdirThere you go. Was too lazy for an interdiff ;)
Comment #12
ParisLiakos commentedready to fly, thanks:)
Comment #13
twistor commentedAnd what about BadResponseException?
Comment #14
berdirThat'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.
Comment #15
twistor commentedAhh, right.
Comment #16
alexpottCommitted 28f278b and pushed to 8.x. Thanks!