| From: Lifeng Zhao <lifeng.zhao@linkplay.com> | |
| Sent: Sunday, December 12, 2021 5:03 PM | |
| To: Hidden | |
| Subject: Re: Security Vulnerability | |
| *** The Answer *** | |
| Hi Hidden, | |
| Thank you very much for your detailed report on the security vulnerability. It's super helpful and important to us. We'll take the immediate action to fix this. Thank you again for your great support. | |
| Best, |
| It's been a while since this gist was written. In the meantime the package homeassistant-supervised apt | |
| package was introduced for debian based systems. If you used that way the first thing you should do use | |
| the normal package uninstaller with something like: (sudo) apt remove homeassistant-supervised | |
| If for some reason that doesn't work proceed with the below instructions for a manual cleanup. | |
| 1) stop services: | |
| sudo systemctl stop hassio-supervisor.service | |
| sudo systemctl stop hassio-apparmor.service | |
| 2) disable services: |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
Recently when refactoring a Vue 1.0 application, I utilized ES6 arrow functions to clean up the code and make things a bit more consistent before updating to Vue 2.0. Along the way I made a few mistakes and wanted to share the lessons I learned as well as offer a few conventions that I will be using in my Vue applications moving forward.
The best way to explain this is with an example so lets start there. I'm going to throw a rather large block of code at you here, but stick with me and we will move through it a piece at a time.
<script>
// require vue-resource...
new Vue({
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| function dedent(callSite, ...args) { | |
| function format(str) { | |
| let size = -1; | |
| return str.replace(/\n(\s+)/g, (m, m1) => { | |
| if (size < 0) | |
| size = m1.replace(/\t/g, " ").length; |