You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xlq20080808 opened this issue
Nov 28, 2023
· 0 comments
Assignees
Labels
bugSomething isn't working and you are sure it's a bug!pluginPlugin for agent or collector. Be used to extend the capabilities of default implementor.pythonPython agent related
1、 when the service is started, it will try to obtain a snapshot before making method calls. The behavior is expected for an interpreted language like python.
But when the method is actually executed, an None snapshot will cause the trace to interrupt.
2、 After checking the test cases, the writing method in the picture below can behave as expected.
Each method call triggers snapshot = get_context().capture()
But we cannot require users to write this way
Are you willing to submit a pull request to fix on your own?
Yes I am willing to submit a pull request on my own!
bugSomething isn't working and you are sure it's a bug!pluginPlugin for agent or collector. Be used to extend the capabilities of default implementor.pythonPython agent related
Search before asking
Apache SkyWalking Component
Python Agent (apache/skywalking-python)
What happened
python version : 3.11.4
python agent : v1.0.1
flask version: 2.3.0
demo
cross threads are not in one trace
What you expected to happen
Cross threads in one trace
As shown below
How to reproduce
Anything else
1、 when the service is started, it will try to obtain a snapshot before making method calls. The behavior is expected for an interpreted language like python.
But when the method is actually executed, an None snapshot will cause the trace to interrupt.
2、 After checking the test cases, the writing method in the picture below can behave as expected.
Each method call triggers
snapshot = get_context().capture()
But we cannot require users to write this way
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: