Sept 10th 2023
- In
Google Chrome
, go to chrome://settings/adPrivacy - In
Windows
, make sureChrome
is closed, and load the file%LOCALAPPDATA%\Google\Chrome\User Data\Default\Preferences
in a text editor and format it as JSON.
// /////////////////////////////////////////////////////////////////// | |
// index.cjs - this is exported in the manifest for Openwhisk Deploy | |
// Only supported in Node 14+ (dynamic import) | |
async function cjsMain(params) { | |
const { default: esmMain } = await import('./index.mjs') | |
return esmMain(params) | |
} | |
exports.main = cjsMain |
const searchSubstringInRepo = async (owner, repo, substring) => { | |
const repoApiUrl = `https://api.github.com/repos/${owner}/${repo}/git/trees/master?recursive=1`; | |
const headers = { | |
'Accept': 'application/vnd.github+json', | |
'Authorization': 'token YOUR_PERSONAL_ACCESS_TOKEN' | |
}; | |
try { | |
const response = await fetch(repoApiUrl, { headers }); | |
if (!response.ok) { |
# adapted from https://osxdaily.com/2020/07/20/how-convert-macos-installer-iso/ | |
hdiutil create -o /tmp/Monterey -size 13700m -volname Monterey -layout SPUD -fs HFS+J | |
hdiutil attach /tmp/Monterey.dmg -noverify -mountpoint /Volumes/Monterey | |
sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Monterey --nointeraction | |
hdiutil detach /volumes/Install\ macOS\ Monterey |
const path = require('path') | |
const assert = require('assert') | |
function urlJoinPath(url, pathToAdd) { | |
const u = new URL(url) | |
u.pathname = path.posix.join(u.pathname, pathToAdd) | |
return u.href | |
} | |
let result1 = urlJoinPath('https://foo.bar/a/b', 'recordlogin') |
Monterey has a bug that is impacting global mute functionality in the OS when using any audio bluetooth devices such as AirPods. When global OS mute is used it is muting both the input and the output when the desired outcome would be to only mute the input. This problem did not exist on Big Sur. It appears that in macOS Monterey there was a change made to how devices are classified (it is clearly a bug), that change on the backend of the operating system is causing all types of issues for any device that exercised control over headsets or microphones.
if [ $ITERM_SESSION_ID ]; then | |
precmd() { | |
echo -ne "\033]0;${PWD##*/}\007" | |
} | |
fi |
{ | |
"version": "0.2.0", | |
"configurations": [ | |
{ | |
"type": "node", | |
"request": "launch", | |
"name": "Jest All", | |
"program": "${workspaceFolder}/node_modules/.bin/jest", | |
"args": ["--runInBand"], | |
"console": "integratedTerminal", |
find . -type d -name FOLDER_TO_EXCLUDE_FROM_SEARCH -prune -o -type f -name FILENAME_TO_FIND -print | xargs grep PATTERN_TO_SEARCH_IN_FILE |
Estimated time: 10 minutes