After switching to Wayland (with an Intel iGPU on Fedora 39), I started experiencing extreme lag in Chrome.
Here is a workaround:
- Go to chrome://flags
- Search for "ozone" or "wayland"
- Set "Preferred Ozone platform" to "auto"
- Relaunch
My ASUS B760M motherboard and many others have a Nuvoton Super I/O chip used for controlling fans, monitoring temperature and other tasks.
Some of the temperature readings that the chip provides are not connected to any physical sensors. This caused bad readings, like reported by lm_sensors here:
$ sensors nct6798-*
nct6798-isa-0290
Adapter: ISA adapter
Certain expected behaviors in the infrastructure can cause alerts to fire unnecessarily, generating noise and contributing to alert fatigue.
For example, database backups can increase the number of disk operations beyond what is expected during business hours but they don't cause issues that require human actions because they usually run outside business hours.
If these events happen on specific time periods, they can be ignored programmatically.
The goal is to open a different profile for work-related URLs opened anywhere on the desktop.
git-blame shows what revision and author last modified each line of a file.
$ echo "this is a test" > test.txt
$ git add test.txt
$ git commit -m "first commit"
$ git blame test.txt
^d12054e (John Doe 2023-07-20 10:08:32 -0300 1) this is a test
ls -l /dev/nvme1*
)blkid
)uuidgen && xfs_admin -U GENERATED_UUID_HERE /dev/nvme1n1p1
)blkdid
)mount -t xfs /dev/nvme1n1p1 /mnt
)[Unit] | |
Description=JupyterLab | |
After=network-online.target | |
Wants=network-online.target | |
[Service] | |
ExecStart=/usr/bin/jupyter lab --no-browser | |
Restart=on-failure | |
RestartSec=7 | |
RestartPreventExitStatus=3 |
- hosts: all | |
gather_facts: false | |
become: false | |
tasks: | |
- name: Populate ~/.ssh/known_hosts | |
delegate_to: localhost | |
known_hosts: | |
key: "{{ lookup('pipe', 'ssh-keyscan ' + inventory_hostname + ' 2>/dev/null') }}" | |
name: "{{ inventory_hostname }}" |
This is a plugin that verifies if the Ansible version meets the version requirements.
You can use the same range identifiers from Ansible Galaxy, separate by commas:
*: The most recent version. This is the default.
!=: Not equal to the version specified.
==: Exactly the version specified.