This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that
| # spdx-license-identifier Unlicense | |
| if ($args.count -eq 0) | |
| { | |
| write-host "Pomodoro Timer that locks the workstation (screen) when done." | |
| write-host "Usage: pomodoro.ps1 <minutes> ['activity']" | |
| write-host "Example: pomodoro.ps1 5 try out new script" | |
| Exit | |
| } | |
| # Select default activity if none is specified, otherwise concat all optional arguments |
Setup a dev enviroment on WSL
https://docs.microsoft.com/en-us/windows/wsl/wsl-config#configure-global-options-with-wslconfig
| using namespace System.Management.Automation | |
| using namespace System.Management.Automation.Language | |
| if ($host.Name -eq 'ConsoleHost') | |
| { | |
| Import-Module PSReadLine | |
| } | |
| #Import-Module PSColors | |
| #Import-Module posh-git | |
| Import-Module -Name Terminal-Icons |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
| name: Security audit | |
| on: | |
| schedule: | |
| - cron: '0 0 * * *' | |
| push: | |
| paths: | |
| - '**/Cargo.toml' | |
| - '**/Cargo.lock' | |
| jobs: | |
| security_audit: |
| $path = "your folder path" | |
| Set-Location $path | |
| foreach ($file in (get-childitem $path | where { ! $_.PSIsContainer } )) | |
| { | |
| $year=$file.CreationTime.Year | |
| $month=$file.CreationTime.Month | |
| $day=$file.CreationTime.Day | |
| $ext=($file.Extension).Trim(".") | |
| $newpath=$path,$year,$month,$day,$ext -Join "\" | |
| if (Test-Path $newpath){ |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
| #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. | |
| #Warn ; Enable warnings to assist with detecting common errors. | |
| SendMode Input ; Recommended for new scripts due to its speed and reliability. | |
| WindowTitlesToToggleMinimizedAndFullScreenStates := ["Seinfeld", "13tv.co.il", "ערוץ 13", "ערוץ 12", "חדשות 13", "המסך המפוצל", "VLC"] | |
| ProcessNamesToToggleMuteOn := ["chrome.exe", "brave.exe"] | |
| SoundUpAndDownVolumeStep = 10 | |
| ; Increase or decrease volume using a specific step | |
| ; Originally written to make the Das Keyboard Professional volume knob less annoying, making it behave like it does on MacOS |
