lightweight

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

centos 8.2 已经发布了，想了解下对 centos 8.x 的支持计划大概是怎样的，谢谢。

Describe the bug
When a timed theme switch is delayed due to high GPU usage, the old monitoring module logged this incident.
The new module has been rewritten more efficiently and does not yet implement this behavior.

Expected behavior
The new GPU monitoring module logs the GPU usage once after the threshold has been surpassed with a message similar to the old module, e.g

SSL_shutdown() tries to send the close_notify shutdown alert to the peer. When the peer has shutdown, kernel will send a SIGPIPE to client, so we must catch the signal.

debootstrap.sh replaces extraargs or another line in the environment where it finds 'console=' before the line that starts with console=

Suggested the following fix:

--- a/lib/debootstrap.sh
+++ b/lib/debootstrap.sh
@@ -626,7 +626,7 @@ prepare_partitions()
 	# if we have a headless device, set console to DEFAULT_CONSOLE
 	if [[ -n $DEFAULT_CONSOLE && -f $SDCARD/boot/armbianE