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
Complete the implementation of the Tracer trait. Remove STOP_ITERATION (#29)
I seem to be unable to write Python code that would emit the
STOP_ITERATION event. I've removed it for now
We added support for all other events in the Tracer trait, and tests for
each one.
Signed-off-by: Tzanko Matev <[email protected]>
Currently in print_tracer.rs we have only one test for the CALL event. We want tests for all other events. The test must verify that the corresponding event was raised and handled at least once.Write tests for the complete Tracer trait
4
+
5
+
Currently in print_tracer.rs we have only one test for the CALL event. We want tests for all other events. The test must verify that the corresponding event was raised and handled at least once.
6
+
--- FOLLOW UP TASK ---
7
+
Write tests for the complete Tracer trait\nCurrently in print_tracer.rs we have only one test for the CALL event. We want tests for all other events. The test must verify that the corresponding event was raised and handled at least once.
8
+
--- FOLLOW UP TASK ---
9
+
For each handler in CountingTracer also print the line at which the event fired. Refer to the sys.monitoring API and specifically to the CodeObject type for details.
0 commit comments