BSD Commit Log Search

www/opengist: Update to 1.12.2

Changes since 1.12.1:

v1.12.2

Added

  * Search all fields (#622).
  * Display a form to create an Opengist account coming from a OAuth
    provider (#623).
  * Rebuild search index in admin options (#647).

Fixed

  * Clean file path names on file creation (#624).
  * Support UTF-8 on gist download (#625).
  * CSRF skipper only for GET *.js request (#627).
  * Async-loaded gist embed scripts (#630).

    [7 lines not shown]

   callout(9): Clarify previous language about clarity/efficiency.

   And with that, I think I'm done touching up callout(9) for now.

   PR kern/60288: callout(9) does not document callout_schedule()

[offload] Fix --libomptarget-nvptx-bc-path in tests

PR #198622, which landed as 3383f0d6fe01, causes 272 `libomptarget ::
nvptx64-nvidia-cuda` test fails on my system with:

```
clang: error: bitcode library '/home/jdenny/llvm/build/\./lib/x86_64-unknown-linux-gnu/nvptx64-nvidia-cuda' does not exist
```

This patch fixes that.

   callout(9): Expand some details a bit.

   Prompted by (but not really related to):

   PR kern/60288: callout(9) does not document callout_schedule()

Set PARALLEL_SHUTDOWN for faster guest shutdown

(cherry picked from commit 55dfc35881f108ca22d2a396679cc00e217df09b)

NAS-141131 / 27.0.0-BETA.1 / Set PARALLEL_SHUTDOWN for faster guest shutdown (#18989)

## Problem

On shutdown/reboot, TrueNAS stops containers and VMs one at a time,
waiting up to the per-guest shutdown timeout (90s by default) for each.
With many guests, this serializes into a long wait — a system with 10
containers and 10 VMs can spend most of its shutdown idle, waiting on
guests one after another.

## Solution

Set `PARALLEL_SHUTDOWN` in `/etc/default/libvirt-guests` so all
containers shut down concurrently and all VMs shut down concurrently.
The per-guest timeout is unchanged; the waits just happen in parallel.

libvirt applies `PARALLEL_SHUTDOWN` independently per URI (lxc, qemu),
so the cap only needs to cover the larger batch — hence
`max(len(containers), len(vms), 1)`.

sysutils/tempo: Update 2.7.2 => 2.10.5

Changelog:
https://github.com/grafana/tempo/blob/v2.10.5/CHANGELOG.md

- Fix build with custom user/group not from UIDs/GIDs.
- Fix substitution in comments in rc script.

PR:             295525
Sponsored by:   UNIS Labs
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>

[RISCV] Reserve all sub-registers of user reserved GPRs (#199302)

When a GPR is reserved by the user (e.g., via  `-mattr=+reserve-x27`)
or marked as constant, only the top-level register was being marked
reserved in `RISCVRegisterInfo::getReservedRegs`. Its sub-registers
(`X27_W` and `X27_H`) remained unreserved.

This broke `LiveIntervals` when register pressure tracking was enabled
by #115445. Because the sub-registers were not reserved, the register
unit was considered non-reserved, causing `LiveIntervals` to track its
liveness and crash in the Machine Verifier due to the reserved
register missing from basic block live-in lists.

Instead, we should ensure that reserving a register also reserves all
of its sub-registers, so that the register unit is correctly
identified as reserved and ignored by `LiveIntervals`.

Fixes #176227

   callout(9): Prefer callout_setfunc/schedule more explicitly.

   It is better on clarity grounds; the efficiency difference is really
   quite minor.

   Prompted by:

   PR kern/60288: callout(9) does not document callout_schedule()

   callout(9): Partially fix markup error in previous.

   Tried to spell out that it will call func(arg) and forgot to fix it
   before previous commit.  Doesn't look right now but at least it is
   not as thoroughly wrong as something that renders as Fa(func, arg).
   (This is an invitation for our resident mdoc wizards to correct my
   infelicities!)

   PR kern/60288: callout(9) does not document callout_schedule()

   callout(9): Use .Bl -tag to list functions, not paragraphs of prose.

   Prompted by:

   PR kern/60288: callout(9) does not document callout_schedule()

   callout(9): Clarify callout_schedule, _setfunc, and _reset.

   Might be better to use .Bl -tag instead of paragraphs of prose too.

   PR kern/60288: callout(9) does not document callout_schedule()

   sys/nfs_debug: fixed a typo which brokes show nfsreq /f

   OK: deraadt@

   update to magic-wormhole 0.24.0

   update to microsoft-gsl 4.2.2

   update to py-zipstream-ng 1.9.2

   update to py-iterable-io 1.0.4

   drop myself as maintainer

   Set MODCLANG_VERSION = 22.

   Suggested by tb@, but the build still runs clang-scan-deps-19,
   and we aren't completely shure what happens after the switch
   to llvm-22.

   Mention EMULFKEYS (mac68k).

Initial import of rio, accelerated terminal emulator
While it starts, I was not actually able to test it due to lack of suitable hardware with NetBSD

Update editors/fresh to v.0.3.8

   Document EMULFKEYS for mac68k.

[VPlan] Create casts before ComputeReductionResult (NFC). (#199372)

This ensures ComputeReductionResult is created with operands that have
their correct types set at construction.

   Add commented out EMULFKEYS for emulating function keys on mac keyboards
   without them.

netlink: Avoid potential undefined behaviour

Taking the address of an OOB array element is UB, even if not
dereferenced.

Reviewed by: des, bz
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57172

   Map mode switch to "Command" for US keyboards.

   This was necessary as mapping Command to mode swtich with wsconsctl discards
   the Cmd1 setting and thus cannot be used to switch terminals.

   Support emulated function keys.

   As posted to port-mac68k:
   https://mail-index.netbsd.org/port-mac68k/2026/05/16/msg001080.html

   Support for raw mode mostly from code used with macpcc.

   As posted to port-mac68k:
   https://mail-index.netbsd.org/port-mac68k/2026/05/16/msg001080.html

[gn build] Port commits (#199375)

170d37d861b0
1b0e603087b6
9997b11c6469