Tessa Walsh

@karenhanson Thanks for flagging this. When the version of the crawler with Playwright is released, it will be a breaking change and will require that custom drivers are converted to...

Hi @gitreich! Oops, I think this is a regression that was introduced when we started allowing 4/5xx status codes for pages rather than throwing an error or moving on the...

Ah, I see what happened. We added a `--failOnInvalidStatus` option and were checking that to see if the crawl should fail when a page returned 4xx/5xx, but if `--failOnFailedSeed` is...

In the meantime, can you confirm if you run the crawl with both `--failOnFailedSeed` and `--failOnInvalidStatus` that it works as you'd expect? (i.e. quits with exit code of 1) We...

Ah, got it! When the URL wasn't reachable due to DNS not resolving, the crawler was falling back to the default fatal status code of 17. Putting in a patch...

Hi @gitreich, glad to hear this is working with `--failOnFailedSeed` now! For the other behavior you're describing, I think that may be as expected. In the 1.x releases, if `--failOnInvalidStatus`...

Hi @Abggithub123, thank you for the bug report. On the first issue of the font and theme, it looks like the website always loads the default and then just keeps...

I'm seeing the same behavior described by @ross-spencer with `--processes` with bagit-python version 1.8.1, Python 3.10.9, on a Macbook with M2 chip.

Thanks @borsboomm - if you're able to supply the WACZ so we can reproduce locally that would be very helpful.

> Any news on this? We would like to upgrade our old Debian 11 servers to 12 :) Hi, thanks for your patience and to @edsu for starting this branch!...