Takahiro YOSHIHARA tacahiroy

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.

技術文書の書き方

このメモは、私（@ymmt2005）が長年にわたってソフトウェアプロダクト開発に関わってきて 2022年現在こうしたほうが良いと考えているベストプラクティスです。

科学的な分析等に基づくわけではない経験則であるため、今後も随時見直すことがありますし、ここに書いてあることが常に正しいわけでもあらゆるソフトウェア開発に適するわけでもありません。

しかしながら、実務経験が豊富で、モダンな技術スタックに明るいエンジニアの経験則は一定の役に立つのではないかと考えて記します。

This gist provides a summary on how to accomplish the following tasks:

Access WSL2 using putty
Run Eclipse on WSL2 Ubuntu, displaying the Eclipse UI on VcXsrv running on Windows
- Connecting to VcXsrv directly from WSL2
- Using SSH X11 forwarding, with network connection initiated from Windows to WSL2 Ubuntu, which is particularly useful on company laptops that refuse all incoming network connections on Windows.

Prerequisites:
- WSL2 up and running
- Putty, Plink & PuttyGen installed on Windows

Assigning Static IP Addresses in WSL2

WSL2 uses Hyper-V for networking. The WSL2 network settings are ephemeral and configured on demand when any WSL2 instance is first started in a Windows session. The configuration is reset on each Windows restart and the IP addresses change each time. The Windows host creates a hidden switch named "WSL" and a network adapter named "WSL" (appears as "vEthernet (WSL)" in the "Network Connections" panel). The Ubuntu instance creates a corresponding network interface named "eth0".

Assigning static IP addresses to the network interfaces on the Windows host or the WSL2 Ubuntu instance enables support for the following scenarios:

set http or socks proxy environment variables

# set http proxy
export http_proxy=http://PROXYHOST:PROXYPORT

# set http proxy with user and password
export http_proxy=http://USERNAME:PASSWORD@PROXYHOST:PROXYPORT

# set http proxy with user and password (with special characters)

You can't install it with dpkg because dpkg is not this distro's package manager. It would conflict with xbps. So the dpkg in repo is built without install support. You can attempt to install it manually by doing:

ar x filename.deb

Suppose you want to inject a credential into a Pipeline script. The cloudbees note does not include Pipeline script examples. https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs

The Jenkins Pipeline Docs' description of the git pushmethod doesn't have an example using injected credentials. (https://jenkins.io/doc/pipeline/examples/#push-git-repo)

The Snippet generator is helpful, but not not if you try to follow the instructions at: https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin

	" ~/.vimrc
	" ...

	" Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support
	Plugin 'dense-analysis/ale'

	" ...
	" dense-analysis/ale options
	let g:ale_history_log_output = 1
	let g:ale_use_global_executables = 1

	{
	"defaultProfile": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}",
	"initialRows": 30,
	"initialCols": 120,
	"alwaysShowTabs": true,
	"showTerminalTitleInTitlebar": true,
	"experimental_showTabsInTitlebar": true,
	"profiles": [
	{
	"guid": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}",