-
Notifications
You must be signed in to change notification settings - Fork 633
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
SQLCommenter semicolon bug fix #1200
Merged
srikanthccv
merged 9 commits into
open-telemetry:main
from
Thiyagu55:python-commenter-semicolon-bug
Jul 22, 2022
Merged
SQLCommenter semicolon bug fix #1200
srikanthccv
merged 9 commits into
open-telemetry:main
from
Thiyagu55:python-commenter-semicolon-bug
Jul 22, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Thiyagu55
changed the title
Python commenter semicolon bug fix
SQLCommenter semicolon bug fix
Jul 20, 2022
srikanthccv
approved these changes
Jul 21, 2022
wosc
added a commit
to ZeitOnline/vivi
that referenced
this pull request
Jul 28, 2022
AFAICT otel violates its own API here, should use get_span_context() instead: File "opentelemetry/instrumentation/utils.py", line 160, in _generate_opentelemetry_traceparent _span_id = trace.format_span_id(span.context.span_id) AttributeError: 'NonRecordingSpan' object has no attribute 'context' I'm backporting open-telemetry/opentelemetry-python-contrib#1200 which sidesteps the issue by using propagate to generate the traceparent header instead of doing it manually.
shalevr
added a commit
to shalevr/opentelemetry-python-contrib
that referenced
this pull request
Aug 30, 2022
* main: Codespell ci (open-telemetry#1237) aiohttp-client: Fix producing additional spans with each newly created ClientSession (open-telemetry#1246) Remove support for 3.6 (open-telemetry#853) Added the Licence and Manifest file Restore metrics in django (open-telemetry#1208) fix typo in example codes (open-telemetry#1240) boto3sqs: Make propagation compatible with other instrumentations and add 'messaging.url' span attribute (open-telemetry#1234) Release 1.12.0-0.33b0 (open-telemetry#1223) Fix Flask instrumentation doc link (open-telemetry#1216) Feature/metrics instrumentation urllib3 (open-telemetry#1198) Metric instrumentation asgi (open-telemetry#1197) Metrics instrumentation flask (open-telemetry#1186) Adding sqlalchemy native tags in sqlalchemy commenter (open-telemetry#1206) ci: fix docs workflow failure (open-telemetry#1211) Add psycopg2 native tags to sqlcommenter (open-telemetry#1203) SQLCommenter semicolon bug fix (open-telemetry#1200) Sync with sdk setup from setUpClass to setUp (open-telemetry#1193) # Conflicts: # CHANGELOG.md # instrumentation/opentelemetry-instrumentation-tornado/src/opentelemetry/instrumentation/tornado/__init__.py # instrumentation/opentelemetry-instrumentation-tornado/src/opentelemetry/instrumentation/tornado/client.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR fixes the bug which appends ; before the comment. Ideally it should append ; at the last
Type of change
How Has This Been Tested?
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.