aiohttp-client: Fix producing additional spans with each newly created ClientSession #1246
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
TraceConfigs that are created when a new ClientSession is created were incorrectly added to the effectively global list of trace configs that can be passed as argument to the instrumentor's
instrument
function. The global list then got inject into the arguments to create the ClientSession. With every TraceConfig in the global list an additional span got created per request.This even happened when there wasn't passed any trace config list to the
instrument
function since as default an empty list was used.Fixes #1207
Type of change
How Has This Been Tested?
Adapted existing tests and added a new one.
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.