Yury Semikhatsky fb319e6d3d fix: match client step and server action by explicit stepId (#30641) ... Matching bu `apiName@wallTime` fails when two actions start at the same time, e.g. two parallel api requests. Moreover, it results in trace actions that have parent set to themselves, which in turn causes infinite loop in the trace viewer. To avoid this problems we write stepId explicitly to the library trace and use those step ids to find corresponding test runner steps. The stepId is passed via zone in case of expect, because the protocol step is quite deep in the call chain after or explicitly in case of API call steps created by the test runner instrumentation.		2024-05-14 12:10:46 -07:00
..
DEPS.list	chore: run check-deps for all packages (#21395)	2023-03-03 14:50:43 -08:00
har.ts	chore: fix har date types (#26783)	2023-08-30 12:40:46 -07:00
snapshot.ts	chore: make NodeSnapshot type recursive and more (#30619)	2024-05-08 11:08:40 -07:00
trace.ts	fix: match client step and server action by explicit stepId (#30641)	2024-05-14 12:10:46 -07:00