Notices by Gert van Dijk (gertvdijk@mastodon.social)

Lasse Collin in commit message: “The other maintainer suddenly disappeared.” 😆

#jiatan #xz
https://github.com/tukaani-project/xz/commit/77a294d98a9d2d48f7e4ac273711518bf689f5c4

nginx (by F5) forked as freenginx by long time core developer Maxim Dounin 👀

http://freenginx.org/pipermail/nginx/2024-February/000000.html

https://www.phoronix.com/news/Nginx-Forked-To-Freenginx

#freenginx #nginx #webdev #selfhosting #opensource

#firefox won't open for me when my PC has not internet (e.g. no WiFi or firewall block), but the process appears just 'sleeping' in the process manager. No window appears.

What could be the issue? One of my extensions preventing to start without an internet connection or something?

Starting from the command line there is also zero output.

```
$ firefox

```
(nothing)

OpenZFS 2.2 released.🥳
https://github.com/openzfs/zfs/releases/tag/zfs-2.2.0

Looking forward to that reworked ARC algorithm for a more stable performance.
#zfs #linux

@knurd42 IIUC: Just fetching/cloning anything shallow would be problematic server-load wise then. And then also updating existing clones would (all individual branch HEADs, customized for each state)... ?

Good to be aware about it, but yeah, I think for hammering with CI this doesn't make sense anyway - should be cached CI-side or using plain archives of releases.

Also consider that server-side caching of pack objects which should be hit if it's the same tag for the shallow clone.

@gnomon @jpmens Yes, agree that static file (git-bundle pre-generated) download is probably fastest, but that article predates the Git protocol v2 and the common use of server-side pack objects caches.

See e.g. https://opensource.googleblog.com/2018/05/introducing-git-protocol-version-2.html

Got a huge #git repo to clone you want to speed up? Do a quick first shallow clone, and perform an *unshallow* in the background!

Example with the Linux kernel source tree below.
```
# 234.24 MiB - ready in under a minute
$ git clone --depth 1 --branch v6.2 \
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

$ cd linux # start working!

# downloads remaining ~ 2.00 GiB
$ git fetch --unshallow
```

@clacke ?
My favorite starting point is:
```toml
[tool.mypy]
strict = true
show_error_codes = true
show_column_numbers = true
show_error_context = true
```

Some options in `pyproject.toml` started to work in later / more recent versions for me. E.g. `--strict` did not work for me ~ 1yr ago, but it does now.