Skip to content

Commit 176f8d3

Browse files
committed
Fix line endings and address review comments: collision handling, max attributes limit, multiple predicates support
1 parent d35b4d6 commit 176f8d3

1,420 files changed

Lines changed: 251276 additions & 251258 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.codespellrc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
[codespell]
2-
# skipping auto generated folders
3-
skip = ./.tox,./.mypy_cache,./docs/_build,./target,*/LICENSE,./venv,*/cassettes
4-
ignore-words-list = ot
1+
[codespell]
2+
# skipping auto generated folders
3+
skip = ./.tox,./.mypy_cache,./docs/_build,./target,*/LICENSE,./venv,*/cassettes
4+
ignore-words-list = ot

.coveragerc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
[run]
2-
omit =
3-
*/tests/*
4-
*/gen/*
1+
[run]
2+
omit =
3+
*/tests/*
4+
*/gen/*

.github/CODEOWNERS

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
# This file is only used as a way to assign any change to the approvers team
2-
# except for a change in any of the instrumentations. The actual codeowners
3-
# of the instrumentations are in .github/component_owners.yml.
4-
5-
# Assigns any change to the approvers team...
6-
* @open-telemetry/opentelemetry-python-contrib-approvers
7-
8-
# ...except for changes in any instrumentation.
9-
/instrumentation
10-
11-
# Learn about CODEOWNERS file format:
12-
# https://help.github.com/en/articles/about-code-owners
1+
# This file is only used as a way to assign any change to the approvers team
2+
# except for a change in any of the instrumentations. The actual codeowners
3+
# of the instrumentations are in .github/component_owners.yml.
4+
5+
# Assigns any change to the approvers team...
6+
* @open-telemetry/opentelemetry-python-contrib-approvers
7+
8+
# ...except for changes in any instrumentation.
9+
/instrumentation
10+
11+
# Learn about CODEOWNERS file format:
12+
# https://help.github.com/en/articles/about-code-owners
Lines changed: 74 additions & 74 deletions
Original file line numberDiff line numberDiff line change
@@ -1,74 +1,74 @@
1-
---
2-
name: Bug Report
3-
description: Create a report to help us improve
4-
labels: [bug]
5-
body:
6-
- type: markdown
7-
attributes:
8-
value: |
9-
Thanks for taking the time to fill out this bug report! Please make sure to fill out the entire form below, providing as much context as you can in order to help us triage and track down your bug as quickly as possible.
10-
11-
Before filing a bug, please be sure you have searched through [existing bugs](https://github.com/open-telemetry/opentelemetry-python-contrib/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Abug) to see if your bug is already addressed.
12-
13-
- type: textarea
14-
id: environment
15-
attributes:
16-
label: Describe your environment
17-
description: |
18-
Please describe any aspect of your environment relevant to the problem, including your Python version, [platform](https://docs.python.org/3/library/platform.html), version numbers of installed dependencies, information about your cloud hosting provider, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on main.
19-
value: |
20-
OS: (e.g, Ubuntu)
21-
Python version: (e.g., Python 3.9.10)
22-
Package version: (e.g., 0.46.0)
23-
24-
- type: textarea
25-
attributes:
26-
label: What happened?
27-
description: Please provide as much detail as you reasonably can.
28-
validations:
29-
required: true
30-
31-
- type: textarea
32-
attributes:
33-
label: Steps to Reproduce
34-
description: Provide a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) if possible and the needed steps to reproduce the problem.
35-
validations:
36-
required: true
37-
38-
- type: textarea
39-
attributes:
40-
label: Expected Result
41-
description: What did you expect to see?
42-
validations:
43-
required: true
44-
45-
- type: textarea
46-
attributes:
47-
label: Actual Result
48-
description: What did you see instead?
49-
validations:
50-
required: true
51-
52-
- type: textarea
53-
id: additional-context
54-
attributes:
55-
label: Additional context
56-
description: Add any other context about the problem here.
57-
placeholder: Any additional information...
58-
59-
- type: dropdown
60-
id: contribute
61-
attributes:
62-
label: Would you like to implement a fix?
63-
description: For guidance on how to get started, refer to the [contribution guide](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/CONTRIBUTING.md).
64-
options:
65-
- "No"
66-
- "Yes"
67-
68-
- type: dropdown
69-
attributes:
70-
label: Tip
71-
description: This element is static, used to render a helpful sub-heading for end-users and community members to help prioritize issues. Please leave as is.
72-
options:
73-
- <sub>[React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
74-
default: 0
1+
---
2+
name: Bug Report
3+
description: Create a report to help us improve
4+
labels: [bug]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thanks for taking the time to fill out this bug report! Please make sure to fill out the entire form below, providing as much context as you can in order to help us triage and track down your bug as quickly as possible.
10+
11+
Before filing a bug, please be sure you have searched through [existing bugs](https://github.com/open-telemetry/opentelemetry-python-contrib/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Abug) to see if your bug is already addressed.
12+
13+
- type: textarea
14+
id: environment
15+
attributes:
16+
label: Describe your environment
17+
description: |
18+
Please describe any aspect of your environment relevant to the problem, including your Python version, [platform](https://docs.python.org/3/library/platform.html), version numbers of installed dependencies, information about your cloud hosting provider, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on main.
19+
value: |
20+
OS: (e.g, Ubuntu)
21+
Python version: (e.g., Python 3.9.10)
22+
Package version: (e.g., 0.46.0)
23+
24+
- type: textarea
25+
attributes:
26+
label: What happened?
27+
description: Please provide as much detail as you reasonably can.
28+
validations:
29+
required: true
30+
31+
- type: textarea
32+
attributes:
33+
label: Steps to Reproduce
34+
description: Provide a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) if possible and the needed steps to reproduce the problem.
35+
validations:
36+
required: true
37+
38+
- type: textarea
39+
attributes:
40+
label: Expected Result
41+
description: What did you expect to see?
42+
validations:
43+
required: true
44+
45+
- type: textarea
46+
attributes:
47+
label: Actual Result
48+
description: What did you see instead?
49+
validations:
50+
required: true
51+
52+
- type: textarea
53+
id: additional-context
54+
attributes:
55+
label: Additional context
56+
description: Add any other context about the problem here.
57+
placeholder: Any additional information...
58+
59+
- type: dropdown
60+
id: contribute
61+
attributes:
62+
label: Would you like to implement a fix?
63+
description: For guidance on how to get started, refer to the [contribution guide](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/CONTRIBUTING.md).
64+
options:
65+
- "No"
66+
- "Yes"
67+
68+
- type: dropdown
69+
attributes:
70+
label: Tip
71+
description: This element is static, used to render a helpful sub-heading for end-users and community members to help prioritize issues. Please leave as is.
72+
options:
73+
- <sub>[React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
74+
default: 0

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
contact_links:
2-
- name: Slack
3-
url: https://cloud-native.slack.com/archives/C01PD4HUVBL
4-
about: Or the `#otel-python` channel in the CNCF Slack instance.
1+
contact_links:
2+
- name: Slack
3+
url: https://cloud-native.slack.com/archives/C01PD4HUVBL
4+
about: Or the `#otel-python` channel in the CNCF Slack instance.
Lines changed: 58 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,58 @@
1-
---
2-
name: Feature Request
3-
description: Suggest an idea for this project
4-
labels: [feature-request]
5-
body:
6-
- type: markdown
7-
attributes:
8-
value: |
9-
Before opening a feature request against this repo, consider whether the feature should/could be implemented in the [other OpenTelemetry client libraries](https://github.com/open-telemetry/). If so, please [open an issue on opentelemetry-specification](https://github.com/open-telemetry/opentelemetry-specification/issues/new) first.
10-
- type: textarea
11-
id: related-problem
12-
attributes:
13-
label: What problem do you want to solve?
14-
description: Is your feature request related to a problem? If so, provide a concise description of the problem.
15-
placeholder: Describe the problem and include relevant issue IDs
16-
validations:
17-
required: true
18-
- type: textarea
19-
id: solution
20-
attributes:
21-
label: Describe the solution you'd like
22-
description: What do you want to happen instead? What is the expected behavior?
23-
placeholder: I'd like to ...
24-
validations:
25-
required: true
26-
- type: textarea
27-
id: alternatives
28-
attributes:
29-
label: Describe alternatives you've considered
30-
description: Which alternative solutions or features have you considered?
31-
placeholder: Some potential solutions
32-
validations:
33-
required: false
34-
- type: textarea
35-
id: additional-context
36-
attributes:
37-
label: Additional Context
38-
description: Add any other context about the feature request here.
39-
placeholder: Some related requests in other projects or upstream spec proposals.
40-
validations:
41-
required: false
42-
- type: dropdown
43-
id: contribute
44-
attributes:
45-
label: Would you like to implement a fix?
46-
description: |
47-
For guidance on how to get started, refer to the [contribution guide](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/CONTRIBUTING.md).
48-
options:
49-
- "No"
50-
- "Yes"
51-
52-
- type: dropdown
53-
attributes:
54-
label: Tip
55-
description: This element is static, used to render a helpful sub-heading for end-users and community members to help prioritize issues. Please leave as is.
56-
options:
57-
- <sub>[React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
58-
default: 0
1+
---
2+
name: Feature Request
3+
description: Suggest an idea for this project
4+
labels: [feature-request]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Before opening a feature request against this repo, consider whether the feature should/could be implemented in the [other OpenTelemetry client libraries](https://github.com/open-telemetry/). If so, please [open an issue on opentelemetry-specification](https://github.com/open-telemetry/opentelemetry-specification/issues/new) first.
10+
- type: textarea
11+
id: related-problem
12+
attributes:
13+
label: What problem do you want to solve?
14+
description: Is your feature request related to a problem? If so, provide a concise description of the problem.
15+
placeholder: Describe the problem and include relevant issue IDs
16+
validations:
17+
required: true
18+
- type: textarea
19+
id: solution
20+
attributes:
21+
label: Describe the solution you'd like
22+
description: What do you want to happen instead? What is the expected behavior?
23+
placeholder: I'd like to ...
24+
validations:
25+
required: true
26+
- type: textarea
27+
id: alternatives
28+
attributes:
29+
label: Describe alternatives you've considered
30+
description: Which alternative solutions or features have you considered?
31+
placeholder: Some potential solutions
32+
validations:
33+
required: false
34+
- type: textarea
35+
id: additional-context
36+
attributes:
37+
label: Additional Context
38+
description: Add any other context about the feature request here.
39+
placeholder: Some related requests in other projects or upstream spec proposals.
40+
validations:
41+
required: false
42+
- type: dropdown
43+
id: contribute
44+
attributes:
45+
label: Would you like to implement a fix?
46+
description: |
47+
For guidance on how to get started, refer to the [contribution guide](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/CONTRIBUTING.md).
48+
options:
49+
- "No"
50+
- "Yes"
51+
52+
- type: dropdown
53+
attributes:
54+
label: Tip
55+
description: This element is static, used to render a helpful sub-heading for end-users and community members to help prioritize issues. Please leave as is.
56+
options:
57+
- <sub>[React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
58+
default: 0

0 commit comments

Comments
 (0)