Merge pull request #1 from open-telemetry/main #2143
Closed
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
* move tracing sdk setup from setUpClass to setUp * Update contrib SHA
* Change tracing to use Resource.to_json() * Edited CHANGELOG * Added PR # to CHANGELOG * Change tracing to use Resource.to_json() * Edited CHANGELOG * Added PR # to CHANGELOG * Generalized removal of empty or blank values * Simplified trace to_json to include empty and null values. Co-authored-by: Diego Hurtado <ocelotl@users.noreply.github.com> Co-authored-by: Leighton Chen <lechen@microsoft.com> Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
…tric reader (open-telemetry#2832) * example * remove test * comments * docs * docs * seconds
…emetry#2771)" (open-telemetry#2839) This reverts commit aa36730. It is no longer required on Python 3.11.0b4 and later; see open-telemetry/opentelemetry-python#2771 (comment) and https://mail.python.org/archives/list/python-dev@python.org/message/73YP4RS4QOJXUS63BQZVLTQHK3OP3L3H/. Specifically, the ^^^^… are now omitted when they would “underline” the whole preceding line, which is the case here, so the expected output is the same as for Python 3.10 and earlier.
…ry#2844) * Instrument instances are always created through a Meter * Fix lint and add changelog * fix lint
* Use force_flush Fixes open-telemetry#2816 * Refactor time out passing * Fix test cases * Add documentation * Add test case * Fix docs * Remove final decorator * Check for timeout in async calls * Remove timeout checking in metric reader * Add force_flush to PeriodicExportingMetricReader * Use TimeoutError * Fix lint * Address timeout comments * Add MetricsTimeoutError * Fix test case
* Update package metadata * support Python 3.6 * address review * update Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com> Co-authored-by: Leighton Chen <lechen@microsoft.com>
* Use devnull instead of stdout when testing console exporter Fixes open-telemetry#2876 * Fix lint * Refactor test case * Debug test in CI * Fix test * Move reset metrics to setup and teardown * Remove repeated code
Co-authored-by: Diego Hurtado <ocelotl@users.noreply.github.com>
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
Co-authored-by: Diego Hurtado <ocelotl@users.noreply.github.com>
Fixes #3584
* Prometheus Exporter sanitize info metric * Update CHANGELOG.md * Test Prometheus exporter target info sanitize * Prometheus exporter paint it black --------- Co-authored-by: Diego Hurtado <ocelotl@users.noreply.github.com>
Fixes #3580
* Update version to 1.23.0.dev/0.44b0.dev * Update SHA --------- Co-authored-by: Diego Hurtado <ocelotl@users.noreply.github.com>
* Fix docker proto tests * Remove changelog
* Separate contrib jobs per instrumentation Fixes #3499 * Separate exporters * Refactor listings * Fix lists
These files do not have the executable bit set in their filesystem permissions, so the shebang lines are not useful. Fixes #3643.
* Don’t pin an exact version of responses for testing In the test dependencies for opentelemetry-exporter-otlp-proto-http, allow `responses >= 0.22.0` rather than `responses == 0.22.0`. These tests use responses in a very straightforward way, and it’s unlikely that they will be affected by any future breaking changes; meanwhile, allowing newer versions helps with compatibility with newer Python interpreter versions and makes distribution packagers’ lives easier. * Upper-bound responses test dependency to the current minor release As requested in: open-telemetry/opentelemetry-python#3642 (comment) --------- Co-authored-by: Diego Hurtado <ocelotl@users.noreply.github.com>
* Add test context for no exception raised Fixes open-telemetry#1891 * Add missing test class
* Handle HTTP 2XX responses as successful in OTLP exporters * Add test cases for 2XX HTTP responses * Add CHANGELOG entry * Fix lint
bring in sync
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.
bring in sync
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.