https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/
Make sure the following options are off:
Disable pre-fetching
https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/
Make sure the following options are off:
Disable pre-fetching
Because of this bug the libnet1 dpkg installation fails.
$ sudo dpkg -i --force-overwrite /var/cache/apt/archives/libnet1_1.1.6+dfsg-3.1build2_amd64.deb
dpkg-deb: error: archive '/var/cache/apt/archives/libnet1_1.1.6+dfsg-3.1build2_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up
dpkg: error processing archive /var/cache/apt/archives/libnet1_1.1.6+dfsg-3.1build2_amd64.deb (--install):
dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
VMware macOS Big Sur 11 - VMX Code | |
smbios.reflectHost = "TRUE" | |
hw.model = "MacBookPro14,3" | |
board-id = "Mac-551B86E5744E2388" | |
smc.version = "0" |
# This script will manually rip out all VMware Tools registry entries and files for Windows 2008-2019 | |
# Tested for 2019, 2016, and probably works on 2012 R2 after the 2016 fixes. | |
# This function pulls out the common ID used for most of the VMware registry entries along with the ID | |
# associated with the MSI for VMware Tools. | |
function Get-VMwareToolsInstallerID { | |
foreach ($item in $(Get-ChildItem Registry::HKEY_CLASSES_ROOT\Installer\Products)) { | |
If ($item.GetValue('ProductName') -eq 'VMware Tools') { | |
return @{ | |
reg_id = $item.PSChildName; |
<hash>
with your gist's hash):
# with ssh
git clone git@gist.github.com:<hash>.git mygist
# with https
git clone https://gist.github.com/.git mygist
On my yourney though hundreds of videos, tutorials and manuals (Bardwell, UAV Tech, JohnnyFPV, Mr. Steele, Le Drib, RotorRiot (sorry, for the missed ones) and wrote down their suggestions). This is the result of my notes. It should provide the least necessary but most compressed information to start tuning and setting your Quadcopter.
In my case I use the widely spread Taranis X7
remote control.
I am a freestyle pilot, so keep in mind, that these settings are in this scope (more smooth, softer flight behaviour).
git_notes.txt -- assumes CLI in Linux/OSX or Cygwin or WSL (Windows SubSystem for Linux). | |
https://git-scm.com/docs/ | |
https://www.atlassian.com/git/tutorials/ | |
--- | |
################################################## | |
### Recommended Windows vs Linux Compatibility ### | |
################################################## | |
# recommended git global environment configs: | |
# windows: |
With GitHub Actions, a workflow can publish artifacts, typically logs or binaries. As of early 2020, the life time of an artifact is hard-coded to 90 days (this may change in the future). After 90 days, an artifact is automatically deleted. But, in the meantime, artifacts for a repository may accumulate and generate mega-bytes or even giga-bytes of data files.
It is unclear if there is a size limit for the total accumulated size of artifacts for a public repository. But GitHub cannot reasonably let multi-giga-bytes of artifacts data accumulate without doing anything. So, if your workflows regularly produce large artifacts (such as "nightly build" procedures for instance), it is wise to cleanup and delete older artifacts without waiting for the 90 days limit.
Using the Web page for the "Actions" of a repository, it is possible to browse old workflow runs and manually delete artifacts. But the procedure is slow and tedious. It is fine to delete one selected artifact. It is not for a regular cleanup. We need
#!/bin/bash | |
TOKEN="" | |
REPO="" # format: username/repository | |
EVENT_TYPE="" | |
curl -H "Accept: application/vnd.github.everest-preview+json" \ | |
-H "Authorization: token ${TOKEN}" \ | |
--request POST \ | |
--data '{"event_type": "${EVENT_TYPE}"}' \ |