tcely

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.

Jellyfin API Authorization

To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.

Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.

Sending authorization values

There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed. It's recommend to use the Authorization header. If header auth isn't an option, the token may be sent through the ApiKey query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.

My thread about which social media accounts I have:

https://fosstodon.org/@tcely/109317571417810234

This is the thread I wrote with helpful tips about moving away from Twitter and getting started on Mastodon:

https://fosstodon.org/@tcely/109501305674813494

See you on Mastodon!

Moved to https://ftvdb.com

Boston, MA:

nsbost02.verizon.net - 71.243.0.14

New York, NY:

nsnyny02.verizon.net - 68.237.161.14

Newark, NJ:

nsnwrk02.verizon.net - 71.250.0.14

	const channels = [...document.querySelectorAll("#main-link.channel-link")].map(e => {
	const [, a, b] = e.href.match("/((?:user)\|(?:channel))/(.*)$");
	const feed = "https://www.youtube.com/feeds/videos.xml?" + (a === "user" ? "user=" : "channel_id=") + b;
	const channelName = e.querySelector("yt-formatted-string.ytd-channel-name").innerText;
	return [feed, channelName];
	});
	if (channels.length == 0) {
	alert("Couldn't find any subscriptions");
	} else {
	console.log(channels.map(([feed, _]) => feed).join("\n"));

	def do_stuff(obj):
	"""Performs some simple processing on `obj`."""
	obj.y = obj.related_obj.x ** 2 + 1 # DB query to fetch `.related_obj`
	obj.save() # DB query to update `obj`


	# Obtain a large queryset for this example.
	qs = MyFurstModel.objects.all()

	# Attempt no. 1: NO GOOD. This direct/naive approach has the advantage of describing

	def chunked_queryset(queryset, chunk_size=10000):
	"""Slice a queryset into chunks. This is useful to avoid memory issues when
	iterating through large querysets.

	Code adapted from https://djangosnippets.org/snippets/10599/
	"""
	if not queryset.exists():
	return
	queryset = queryset.order_by("pk")
	pks = queryset.values_list("pk", flat=True)

	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # allows django to get the client's IP address (see the ipware module)
	proxy_set_header X-Forwarded-Proto $scheme; # allows django to determine that the request is secure (see SECURE_PROXY_SSL_HEADER and request.is_secure())
	proxy_set_header X-Forwarded-Host $host; # allows django to determine the name/addr of the server that the client originally connected to (see request.get_host())
	proxy_set_header X-Forwarded-Port $server_port; # same idea as above, but for port number (see request.get_port())

	USE_X_FORWARDED_HOST = True
	USE_X_FORWARDED_PORT = True
	SECURE_PROXY_SSL_HEADER = ("HTTP_X_FORWARDED_PROTO", "https")