Dmitry Gozman
Dmitry Gozman
It seems like the issue has been resolved. If you still encounter problems, please file a new issue with a repro and link to this one.
@UndefinedOffset We have to reproduce this issue locally to be able to debug it. Please fill in all the details of the "Bug Report" template.
@UndefinedOffset Thank you for the repro! Unfortunately, I had no luck reproducing the issue. I ran all tests ~200 times, with and without `CI=1` flag, and every single time both...
We have to reproduce this issue locally to be able to debug it. If you can provide a full repro, please file a new issue by filling the "Bug Report"...
Closing as per above. I don't think we'll be implementing the original feature request.
@gskierk `APIRequestContext` follows the [fetch spec, step 12](https://fetch.spec.whatwg.org/#http-redirect-fetch). I'd recommend to pass [`maxRedirects: 0`](https://playwright.dev/docs/api/class-apirequestcontext#api-request-context-fetch-option-max-redirects), and then follow the redirect manually.
@apis3445 That's probably because you have multiple pages in a single test. For example, I see `{ page }` being used in `beforeEach()` and `test()`, although it looks like they...
@thnk2wn These traces are indeed corrupted. Unfortunately, we are not sure how this happened, so any repro would be very helpful. Even if it only reproduces sometimes.
@thnk2wn Could you please try upgrading to `@playwright/[email protected]`? There have been tracing changes between 1.33 and 1.34, so it might be that the issue has been already fixed?
@17Amir17 Any chance you could share a repro that produces corrupted traces?