脆文:https://www.threads.com/@thecat88tw/post/DS__HXfkROF
謝謝 @cab_late 花時間仔細閱讀並如此詳細的回應我的貼文,這兩天跨年比較忙,今天終於有時間坐下來針對他的疑慮提出幾點說明,大家參考看看,希望有幫助。
首先要先對 functionl call 的本質與目地有清楚的認知。
它是讓 LLM 操作外部資料(side effects)的主要途徑,也是最底層的基礎手法。
脆文:https://www.threads.com/@thecat88tw/post/DS__HXfkROF
謝謝 @cab_late 花時間仔細閱讀並如此詳細的回應我的貼文,這兩天跨年比較忙,今天終於有時間坐下來針對他的疑慮提出幾點說明,大家參考看看,希望有幫助。
首先要先對 functionl call 的本質與目地有清楚的認知。
它是讓 LLM 操作外部資料(side effects)的主要途徑,也是最底層的基礎手法。
Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.
Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1
| 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: |
Note on sizes: a lot of those might be inaccurate as there might be many microservices required aside from the core release/docker image. I haven't tested these recently so I'm not sure
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; |