Tessa Walsh

Hi @lasztoth and @obrienben, I'm having some health issues that have limited my capacity at the moment. I'll be out of the office next week but will try to prioritize...

Hi, thanks @obrienben! This is in scope for the IIPC-funded pywb work, which is due to be delivered end of March, so we will be working on this in the...

Thank you @Schoeneh for the bug report. In the meantime if you need an immediate solution, `--diskUtilization 0` disables the check.

> @tw4l what do you think would make sense here? Perhaps just adding a --title and --desc flags, or a more extensive metadata json blob in the config? I think...

@markpbaggett Initial PR is merged and the 0.9.0 release of the crawler will include `--title` and `--description` CLI args :) Thanks for the full example of the metadata you'd like...

Thanks for the feedback, @ydyote! Yes, the crawler should validate to say that 100 is out of range. In the meantime while we triage this issue, if you'd like to...

> Added in interactive debugging with VSCode in last commit too. Didn't really work out of the box with Skaffold. It is more aimed than I realised at doing everything...

Thanks for the notes @robert-1043 ! It's very possible the pixel size information for the `fullPage` screenshot is incorrect - the image will be whatever height is necessary to capture...

Thanks for the clarification! It looks like puppeteer is setting the pixel sizes in the image metadata according to what the initial display viewport is set at, hence the incorrect...

@robert-1043 can you try from this branch and see if you still have the issue? https://github.com/webrecorder/browsertrix-crawler/tree/full-page-screenshot-pixel-metadata-fix