Jelle van der Waa
Jelle van der Waa
That would require us to use SPICE and then write a custom spice to browser channel. This doesn't seem fairly realistic for us to support in the short term.
The comment above is a phising attempt, don't click it.
We do use the python3-pcp package for our integration tests and unit-tests, we also have a tox venv setup for testing older Python's for example 3.6 which is not in...
We'll need to create an issue [here](https://github.com/cirruslabs/cirrus-ci-docs/issues).
This isn't good enough, it still flakes.
> I believe this is about the archlinux package repository using this command in a packaging script Yes, we run ` "./$pkgname" --man-page >"$pkgname.1"` which thus records the build machine's...
This no longer works
Can you provide more information, what errors do you get, from what Cockpit version did you upgrade? We still run websocket unit tests and they pass on main.
The `not-supported` message is interesting, it can come from cockpit-ws or cockpit-bridge. How do you exactly connect to the websocket?
PQ support seems possible in Python with the `ssl` module and OpenSSL >= 3.5 by loading two certificate chains: ```python import http.server import ssl context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) context.load_cert_chain(certfile="localhost-mldsa.crt", keyfile="localhost-mldsa.key") context.load_cert_chain(certfile="localhost-rsa.crt",...