You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Git Commit Freeze Due to GPG Lock Issues (Solution)
Git Commit Freeze Due to GPG Lock Issues
If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.
Solution Steps
1. Check for GPG Lock Messages
Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.
Duplicate TTY serial port using socat in Python to log everything that goes through it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will work with either networkd or NetworkManager as a resolver. In fact, this is the only way to do bridged KVM
(libvirtd) networking with NetworkManager.
If you're using NetworkManager (on a desktop or laptop, for example) on your KVM host, follow these instructions to set up a bridge interface.
Once you have the host bridge set up, proceed as follows:
Create a bridge network device inside KVM. Edit and save the below text as file host-bridge.xml:
Add a bridge interface to Ubuntu desktop using nmcli
Had to do this for some advanced networking with KVM, and couldn't figure out how to do it using the Nework Manager gui.
Did find an article later that showed how to do it with nmtui, but it's so much easier to record what you did when using
the cli.
IMPORTANT SAFETY TIP: Adding or removing PCI devices, like discrete graphics cards, almost always results in changing the "predictable device name" of your physical network card. This can be prevented by the addition of a simple udev rule (see below).
In the examples below "eth0" is the name of my physical interface. By default on Ubuntu and most distributions that will almost certainly be different, for example: "eno1", "ens1", or "enp2s0".
To see what everything looks like before starting:
Inheritance and Virtual Table are often used to create interface in C++ polymorphic class
What if ... there were another way to do this ?
easier, cleaner, faster and more reliable
This article explains how to use CRTP, [std::variant](https://en.cppreference.com/w/cpp/utility/variant and std::visit to increase code performance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[How To] Force a specific USB device to a certain TTY
Scenario:
multiple USB devices plugged via hub to a host (Linux OS based),
multiple services/programs interacting with TTY running on top (e.g. GPSd)
Problem:
At boot TTY are randomly assigned to devices causing depending services/programs instabilities.
They could indeed fail to start because of different TTY configurations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters