Liang Gong
Liang Gong
@KomalAgarwal1 MemLab doesn't support Firefox for now. The `setup` callback has a `page` parameter, please use that instead of creating your own, otherwise MemLab cannot navigate through the page or...
@KomalAgarwal1 Can you share the scenario file (with the page parameter)? > Observed the same script is working in Puppeteer(stand alone version) for the same chromium version. What kind of...
@KomalAgarwal1 earlier you mentioned: > Observed the same script is working in Puppeteer(stand alone version) for the same chromium version. > Chrome Version is 101.0.4950.0 So I was asking which...
@KomalAgarwal1 Also thanks for sharing the script, I see it no longer contains the `await puppeteer.launch({ product: "firefox" });` statement. Is it working right now? Or do you still get...
@KomalAgarwal1 Can you share the full error message? (including the `interaction fail, making 1 more attempt(s)...` part) > I was asking which puppeteer + chromium version you are using that...
Ah ok, I thought the error message was incomplete because of the line separator. This part is interesting: ``` Expected: https://hostportalperf.cbrehost.com/login Actual: https://hostportalperf.cbrehost.com/browserError.html ``` I guess `https://hostportalperf.cbrehost.com` has some sort...
yeah I know, memlab sets a default user agent string here: https://github.com/facebookincubator/memlab/blob/main/packages/core/src/lib/Constant.ts#L21 For now, there is no option to set the user agent in MemLab CLI (we can add one)....
@KomalAgarwal1 looks like you are building on Windows, please build with Git Bash
@KomalAgarwal1 That's strange. I would recommend a few things to try: 1. Set `defaultUserAgent` to `null`. In that case MemLab will use Chromium's default userAgent. 2. When you run `memlab...
@KomalAgarwal1 Here are all the puppeteer configs in MemLab, you can start by removing all of the configs and add them back one by one and see which puppeteer config...