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.

Sign up for GitHub

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

Jump to bottom

fix: use debug logging level for OpenTelemetry message #442

Merged
merged 5 commits into from Jan 11, 2021
Merged

fix: use debug logging level for OpenTelemetry message #442

merged 5 commits into from Jan 11, 2021

Commits on Dec 21, 2020

  1. fix: use debug logging level for OpenTelemetry message

    @tswast
    tswast committed Dec 21, 2020
    Copy the full SHA
    dc39d0f View commit details
    Browse the repository at this point in the history

  2. only warn at span creation time

    @tswast
    tswast committed Dec 21, 2020
    Copy the full SHA
    5cc4e72 View commit details
    Browse the repository at this point in the history

  3. add unit test for skipping warning

    @tswast
    tswast committed Dec 21, 2020
    Copy the full SHA
    43636f1 View commit details
    Browse the repository at this point in the history

Commits on Jan 11, 2021

  1. Merge remote-tracking branch 'upstream/master' into issue441-telemetr… 

    …y-warning
    @tswast
    tswast committed Jan 11, 2021
    Copy the full SHA
    2551dec View commit details
    Browse the repository at this point in the history

  2. refactor: rename _warned_telemetry to indicate private and mutable

    @tswast
    tswast committed Jan 11, 2021
    Copy the full SHA
    fe5b4e6 View commit details
    Browse the repository at this point in the history