Ilya Kreymer
Ilya Kreymer
Still need: - tests - validation of selectors?
There's not an easy repro step unfortunately, but the usage pattern is to call evaluate() on the iframes on the page to extract links, a simplified version is: ``` try...
The above example that you have has a rejected promise in a different part of the code, here: https://github.com/puppeteer/puppeteer/blob/main/packages/puppeteer-core/src/cdp/ExecutionContext.ts#L532 which is indeed caught. The above stack trace that was reported...
> With #13139 the stack trace should be correct for this case. Could you try to reproduce it again if you have a chance? thanks! Thanks for the update and...
Priority is for zstd encoded content first, but would also be great to support zstd compressed WARCs which are also in use. Will look at https://github.com/101arrowz/fzstd first, also considering WASM...
Hi @jswrenn - that's really strange, I tried to repro it locally with exact same command and it worked fine! What environment are you deploying in? docker/podman/etc.. and os? Another...
Ah, the link extraction happens before autoscrolling at the moment.. However, the new autoclick behavior might be able to address that, now available in 1.5.0 beta.
@benoit74 #753 adds more consistent usage of exit codes - do you want to expand on that with a follow up PR to add distinct ones that you'd like to...
Could there be a way to create warcs with certain size after one RUN (combinewarc / rolloversize...)
Not quite sure what you mean - using `--rolloverSize` + `--combineWARC` together should work as you describe. The combineWARC operation combines all the WARCs in a collection folder after each...
Could there be a way to create warcs with certain size after one RUN (combinewarc / rolloversize...)
> same question for the use of several crawlers in browsertrix: How could an overall max size be configured, which generates x slices of max size and only one smaller...