-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add monocle version changes and fix tests #64
Conversation
Signed-off-by: Kshitiz Vijayvargiya <[email protected]>
Signed-off-by: Kshitiz Vijayvargiya <[email protected]>
…itiz/update_test
Signed-off-by: Kshitiz Vijayvargiya <[email protected]>
Signed-off-by: Kshitiz Vijayvargiya <[email protected]>
add span.type in workflow span |
@@ -4,12 +4,10 @@ name: Tox | |||
|
|||
on: | |||
push: | |||
branches: [ "main" ] | |||
branches: [ "main", "kshitiz/update_test" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls revert this to main
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, just fixing the last failing test
src/monocle_apptrace/wrap_common.py
Outdated
|
||
try: | ||
sdk_version = version("monocle_apptrace") | ||
span.set_attribute("monocle_sdk_version",sdk_version) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can the attribute be monocle-apptrace.version
to reflect the package name
as in https://pypi.org/project/monocle-apptrace/0.1.1/
…itiz/update_test
Signed-off-by: Kshitiz Vijayvargiya <[email protected]>
Signed-off-by: Kshitiz Vijayvargiya <[email protected]>
Proposed changes
Added monocle version in span
Fix tests
Types of changes
What types of changes does your code introduce to this project?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...