Update Guzzle to 6.3#29773
Conversation
7dd50a4 to
94e00fd
Compare
Codecov Report
@@ Coverage Diff @@
## master #29773 +/- ##
============================================
- Coverage 64.01% 63.77% -0.25%
- Complexity 18560 18563 +3
============================================
Files 1171 1171
Lines 69841 69814 -27
Branches 1267 1267
============================================
- Hits 44709 44521 -188
- Misses 24762 24923 +161
Partials 370 370
Continue to review full report at Codecov.
|
658c8ed to
5fb9844
Compare
f82f06d to
ea11974
Compare
ea11974 to
6285911
Compare
453a58f to
2897446
Compare
2897446 to
1f79f03
Compare
7846bc1 to
028e69a
Compare
4889295 to
6d4013e
Compare
b72ff7b to
9dd3caa
Compare
9166ebb to
4141e88
Compare
|
Note: I will rebase and sort this out late Friday. |
|
Rebased. ToDo:
|
|
@PVince81 @DeepDiver1975 or whoever. Can you comment on #29773 (comment) - the "ordinary" 5 unit test fails. And now I am getting other unit tests fails only in the objectstore job: I suspect that one of you will know straight away why this is, rather than me spending lots of time trying to work out what is going on... Edit add: and now a look at it again, it looks like there are changes needed for Guzzle v6 in files_primary_s3, which is enabled for a job in the test matrix. So that (like lots of other app stuff) will need coordination... |
|
@phil-davis maybe we first need to make phan happy: |
DeepDiver1975
left a comment
There was a problem hiding this comment.
left some minor comments ....
| $exception = $this->getMockBuilder('\GuzzleHttp\Exception\ClientException') | ||
| ->disableOriginalConstructor()->getMock(); | ||
| $response = $this->getMockBuilder('\GuzzleHttp\Message\ResponseInterface') | ||
| $response = $this->getMockBuilder('\Psr\Http\Message\ResponseInterface') |
There was a problem hiding this comment.
Should all getMockBuilder() calls use ::class - e.g. 1 line above here that has not been touched by the PR (yet)?
There was a problem hiding this comment.
anywhere a class name is referenced please use ::class
Usually I do this when touching any test case - and then for all occurrences.
Please have a look at https://plugins.jetbrains.com/plugin/7622-php-inspections-ea-extended- - help with this on file level.
| $exception = $this->getMockBuilder('\GuzzleHttp\Exception\ClientException') | ||
| ->disableOriginalConstructor()->getMock(); | ||
| $response = $this->getMockBuilder('\GuzzleHttp\Message\ResponseInterface') | ||
| $response = $this->getMockBuilder('\Psr\Http\Message\ResponseInterface') |
| @@ -191,16 +192,17 @@ public function userHasCreatedACalendarNamed($user, $name) { | |||
| $davUrl = $this->featureContext->getBaseUrl() | |||
| . '/remote.php/dav/calendars/' . $user . '/' . $name; | |||
There was a problem hiding this comment.
"/remote.php/dav/calendars/$user/ $name";
There was a problem hiding this comment.
This was not introduced in the PR.
Refactoring of string concatenation for acceptance test code is in PR #32336
| public function setUp() { | ||
| parent::setUp(); | ||
| $this->config = $this->createMock('\OCP\IConfig'); | ||
| $this->response = $this->createMock('\Psr\Http\Message\ResponseInterface'); |
There was a problem hiding this comment.
@DeepDiver1975 I was "hacking around" here sorting out what happened in Guzzle6 to the client and responses...
- Is this the right sort of thing to do for the unit tests here?
- Should this also have
::class? or it's OK being an interface?
There was a problem hiding this comment.
- createMock looks good
- and yes - use ::class here as well
|
@DeepDiver1975 I have fixed up what I can. Maybe next we need to make a PR/branch in |
|
all apps which use guzzle need adoptions .... files-primary_s3, google, onedrive ....... |
|
@PVince81 @DeepDiver1975 @patrickjahns |
I suggest we plan this for the next server sprint - which starts next week. Vincent will be back by then as well. |
|
See PR #32537 for the next iteration. That is the Guzzle V6 code rebased and refactored for the underlying refactoring of acceptance test code that happened today. That introduced |
Description
Update Guzzle to 6.3, and also other libraries (deleted and regenerated composer.lock)
Related Issue
Motivation and Context
Guzzle 5.3 is outdated, needs update.
Also some libs used by apps will need Guzzle > 6.
How Has This Been Tested?
Types of changes
Checklist:
This is a newer version of #29211 made by cherry-pick and reorganize of the commits from there, to massage it all into these "logical" commits.