apteryks

For the record, the only two files need to run the test suite which are not in a git checkout are these: - selenium/webdriver/remote/getAttribute.js - selenium/webdriver/remote/isDisplayed.js I have no idea...

Right, these files seem to be generated or minified and copied as part of the `prep` Rake task: https://github.com/SeleniumHQ/selenium/blob/trunk/Rakefile#L532. Unfortunately you can't simply involve `rake prep`; as this requires Bazel.

@jgerrish it's always good to have bugs fixed; even if it's not merged by upstream in a timely fashion, distributions can apply the patch on their own :-).

I too have been looping the various options in the `man btrbk.conf`, trying to get a clue, in vain. My intuition was that `target_preserve_min` be the lower bound retention policy...

A "solution" appears to be this: https://src.fedoraproject.org/rpms/python-pydata-sphinx-theme/blob/rawhide/f/prepare_vendor.sh, which is a bit overly complex to my taste.

I also see the same behavior on GNU Guix: ``` test api::test::lookahead_size_properly_bounded_16 ... ok test result: ok. 394 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in...

See: https://github.com/proot-me/proot/issues/286#issuecomment-1019532072.

@oxr463 Hello, I just did (using the 5.3.0 tag); there are still many failures; see the attached build log. [cmxaigk250m4q8imdgpmp3vcdayvqws3-proot-5.3.0.drv.gz](https://github.com/proot-me/proot/files/7921012/cmxaigk250m4q8imdgpmp3vcdayvqws3-proot-5.3.0.drv.gz)

Hi, > Please do not disable the tests, especially the ones that fail saying `UNSAFE`. It says `UNSAFE` because it indicates that the code being tested is failing in an...

Hi! > Upon closer inspection, I see that the two `UNSAFE` failures are due to the fact that you are using `[email protected]`. `org-ql` 0.5 explicitly depends on `org-super-agenda` 1.2, because...