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

[fix] Add back acquire limiter span #1026

Merged
merged 4 commits into from
Mar 29, 2019

Conversation

robert3005
Copy link
Contributor

Before this PR

There was no way to measure time spent in acquire limiter

After this PR

==COMMIT_MSG==
OkHttp: enqueue span is renamed to OkHttp: execute and gets OkHttp: execute-enqueue for time spent acquiring limiter and OkHttp: execute-run for execution of the call
==COMMIT_MSG==

Possible downsides?

@robert3005 robert3005 requested a review from a team as a code owner March 29, 2019 19:01
@robert3005 robert3005 changed the title [fix] Add back limiter span [fix] Add back acquire limiter span Mar 29, 2019
@iamdanfox
Copy link
Contributor

iamdanfox commented Mar 29, 2019

Looks great 👍

@bulldozer-bot bulldozer-bot bot merged commit 21451ba into develop Mar 29, 2019
@bulldozer-bot bulldozer-bot bot deleted the rk/add-back-acquire-limiter-span branch March 29, 2019 19:42
com.squareup.okhttp3:logging-interceptor:3.13.1 (1 constraints: d608d786)
com.squareup.okhttp3:okhttp:3.13.1 (5 constraints: 8745dcdf)
com.squareup.okhttp3:logging-interceptor:3.14.0 (1 constraints: d608d786)
com.squareup.okhttp3:okhttp:3.14.0 (5 constraints: b3456615)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Decent number of changes went into https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3140. Seems like they're getting further and further away from a version of conscrypt that still works on Centos6 :/

bulldozer-bot bot pushed a commit that referenced this pull request Apr 3, 2019
…ody NoSuchMethodErrors (#1039)

## Before this PR

#1026 (which went into 4.20.1) inadvertently brought in a bump in okhttp to 3.14.0.
One of our internal libraries relied on `UnrepeatableRequestBody` which got removed in github.com/square/okhttp/pull/4676, and a solution using `RequestBody#isOneShot` couldn't be made that exhibits the previous behaviour.

## After this PR

Downgrading okhttp to 3.13.1, and adding a constraint to prevent accidental upgrades to 3.14.0 for the time being.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants