@kezhenxu94 I think with using graceful shutting down, we need a simple e2e to verify whether OAP and UI could be shut down successfully. Because, once we have one unexpected thread, the shutdown wouldn't work.

Originally posted by @wu-sheng in apache/skywalking#7020 (comment)

Describe the bug
The markup version of the readme that is displayed in the main page for this repo contains the following links:
Status code [404:NotFound] - Link: https://keyword-2-ecd7b.firebaseapp.com/
Status code [404:NotFound] - Link: https://github.com/GoogleChromeLabs/quicklink/blob/master/#custom-ignore-patterns

(The links in the readme’s markdown may appear different to the link

There's a lot of place for improvement of the documentation.

• Update the Angular guide to use ngx-build-plus
• Improve the API documentation explaining the configuration properties
• Include a guide showing how to use Guess.js with JWT instead of OAuth
• Include Gatsby guide

The content of the documentation is in the GitHub page [repo](https://github.com/guess-js/guess-

To boost the minification we have some mangle properties in the Terser config.
https://github.com/Zizzamia/perfume.js/blob/master/rollup.config.ts

But over time we stopped using most of them, I think it's time to double-check which one are the properties are not necessary anymore.

The current badge overlay close button will remove the badge from the page, but will not persist the badge closure during your session. This might be surprising to developers (e.g I see my metrics -> close badge -> CLS wasn't final and just updated -> whoops here's the badge again).

Few options....

1. Clicking close will be the same as disabling the overlay for the particular tab (i.e we upd

Some prior art here:

https://github.com/puppeteer/examples/blob/master/verify_sw_caching.js
https://michaljanaszek.com/blog/test-website-performance-with-puppeteer/#cacheAndServiceWorker