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 的支持计划大概是怎样的，谢谢。

Description

Scrolling with a trackpad is way too fast.

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.

Description

Remove conflicted patch 0036, and then fix it in old h616_0005 patch , to support reboot

How Has This Been Tested?

Tell if you made a test build.

• made a test build and boot

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-und