When publishing public scoped packages you might get the following errors:
npm ERR! code E402
npm ERR! 402 Payment Required - PUT https://registry.npmjs.org/.... - You must sign up for private packages
This happens when trying to publish public scoped packages. The default access level is private. To resolve this you can either set npm config set access public or add the following to your package.json:
If you have a large spreadsheet to edit (ie. 10k+ columns) with your UHD display (ie. 4K or higher resolution) in Microsoft 365 Excel you may have some performance issues when scrolling.
I just found an easy hack that works for me:
Check Disable hardware graphics acceleration in Excel under File – Options – Advanced – Display section
Exit Excel
Change your display resolution to 1920×1080
Change text scale to 100%
Open the spreadsheet you need to edit with Excel
Change your display resolution back to native resolution
Change text scale back to your original option (ie. 200%)
See magic happens
This hack works until you exit your Excel. So you have to redo step 3-8 when openning new documents.
If you got the following error message when run npm update -g:
$ npm update -g
npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name ".DS_Store": name cannot start with a period
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/sparanoid/.npm/_logs/2021-04-28T13_59_32_013Z-debug.log
Simply run if you installed your Node.js via Homebrew:
find /usr/local -name '.DS_Store' -type f -print -delete
# Make pyenv play nice with Homebrew
# https://github.com/pyenv/pyenv/issues/106
alias brew="env PATH=(string replace (pyenv root)/shims '' (echo $PATH)) brew"
A HomeKit enabled motion sensor. I use Aqara Motion Sensor Hue Motion Sensor
The update interval of Hue Motion Sensor exposes to HomeKit is 10 seconds. Far better than Aqara Motion Sensor (120 seconds). And seems more stable after testing for months.
You want to stick with local automation instead of configuring automations in vendor specific apps
Trigger an open/turn on/start event when motion detected
When no motion for specific minutes. Trigger another event to close/turn off/stop
Why? This method no longer depends on the buggy HomeKit built-in “Turn Off” and Stops Detecting Motion feature. Common HomeKit motion sensors only update the motion state every seconds. When Stops Detecting Motion triggers. It won’t be canceled or delayed when it detects another motion during the detection interval. That causes your accessory to be turned off even motion detects during the time you set.
With my method. Your accessory won’t be turned off if your motion sensor detects motion during the specific time you set. Make your motion sensor work more like an occupancy sensor.
The delay time is in milliseconds so 300000 equals 6 minutes here.
In your Home app. Create the following automations:
First Automation
When: Living Room Motion Sensor – Detects Motion
Accessories:
Turn on your accessory
Turn on your Living Room Delay Switch
Second Automation
When: Living Room Delay Switch Trigger – Detects Motion
Accessories:
Turn off your accessory
Third Automation
This automation is important. It can ensure your accessory can still be turned off at a specific time if the accessory was opened/turned on/started manually.
This is the minimal guide for installing LineageOS 17.1 on OnePlus 3T abtracted from LineageOS offical guide. It works at the time of writing so no gurantee for further updates.
Enable OEM unlocking and USB debugging on your phone with developer mode.
Run adb reboot bootloader to boot your phone into bootloader mode. Also make sure your phone can be find in fastboot mode by re-typing fastboot devices.
Run fastboot flash twrp-3.4.0-0-oneplus3.img to flash custom recovery.
Run fastboot boot twrp-3.4.0-0-oneplus3.img to boot into new recovery mode.
seconds. When Stops Detecting Motion triggers. It won’t be canceled or delayed when it detects another motion during the