games/openbve: update OpenBVE to version 1.14.0.3
Put back the <HintPath> tag for System.ValueTuple
which is missing in this release to fix the build.
Reported by: portscout
www/code-server: Update to 4.136.2
Word wrapping now accounts for injected text, decorations and inlay
hints. Terminal commands executed by extensions start without delay.
Adds an experimental compact layout density option. This release
replaces the withdrawn 4.136.0 and 4.136.1.
Changelog: https://github.com/coder/code-server/releases
Sponsored by: Netzkommune GmbH
pfctl(8): Remove superflous parenthesis
Since apropos(8) uses case-insensitive regular expressions by default
for both manpage names and descriptions, pfctl appears in results
regardless of the parenthetical initialism.
MFC after: 1 week
Reported by: ziaee@
games/linux-enemyterritory: Fix sound
The game starts writing audio s_mixPreStep seconds into the sound
buffer, but s_mixPreStep defaults to 0.05 (50ms), and sound(4) hands out
a ~46ms buffer by default (hw.snd.latency=2), so 50ms is already past
the end of the buffer and nothing is ever written. Start writing at 20ms
instead, which leaves space for sound to be written.
Approved by: arrowd, arved
PR: 251660
Sponsored by: The FreeBSD Foundation
emulators/dosbox-staging: Update to 0.83.0
Switch to CMake, Meson is not supported anymore. ALSA and FLUIDSYNTH
support could be made optional again by patching build files, however
I do not want touch them more than required for building DOSBox.
Release notes: https://www.dosbox-staging.org/releases/release-notes/0.83.0/
devel/py-virtualenv: Update to 21.7.9
- Disable test target due to the following startup error:
pluggy._manager.PluginValidationError: Plugin 'black' for hook 'pytest_collect_file'
hookimpl definition: pytest_collect_file(file_path, path, parent)
Argument(s) {'path'} are declared in the hookimpl but can not be found in the hookspec
See https://github.com/pytest-dev/pytest/issues/14651
- Pet portfmt
ChangeLog: https://github.com/pypa/virtualenv/releases/tag/21.7.9
Reported by: "github-actions[bot]" <notifications at github.com>
tpm: crb: make the Pluton startmethod more resilient
The original implementation assumed that the start/reply doorbells
lived within the device _CRS space, but that isn't always the case. On
my AMD Ryzen 7640U-based frame.work laptop, device memory runs from
0xc0500000-0xc0500fff while the doorbells are up around 0xc0508000.
Stop sanity checking the addresses and just map them in to work reliably
whether they're within the device range or not.
pluton_wait_reply is cribbed from tpm_wait_for_u32, but rewritten
slightly to read in just one place and to read one last time before
giving up at the end of the timeout, just in case.
Reviewed by: kbowling
Differential Revision: https://reviews.freebsd.org/D59327
syslogd/tests: Amend a test to catch leaked process descriptors
This serves to catch the regression fixed by commit
1a669b66ddb4 ("syslogd: reap pipe children on config reload").
MFC after: 1 week
(cherry picked from commit 231dfc99a08874c269593c2e491ce16a618f4ed6)
pf: Re-optimize state key handling
pf states may be looked up using one of two keys: the stack key or the
wire key. For states involving address translation, these will be
distinct; the stack key describes the addresses seen by the local
network stack, and the wire key has the translated addresses.
Historically, pf would avoid allocating separate keys if both are
identical. This changed in commit fcdb520c1b4e ("pf: nat64") to always
allocate separate state key structures. Incidentally, OpenBSD seems to
maintain the optimization, but also has an explicit reference count
embedded in state keys.
The change breaks another optimization: pf_state_key_attach() still uses
state key pointer equality to check whether the stack and wire keys are
equal, so those checks are always false after the aforementioned commit.
Thus we never skip the second key lookup, even when that's possible
(i.e., no address translation is involved).
[15 lines not shown]
syslogd: reap pipe children on config reload
On SIGHUP reload, closelogfiles() frees each F_PIPE filed even when its
pipe process is still running. close_filed() sets f_type to F_UNUSED
before the check, so the condition f_type != F_PIPE is always true and
the filed is freed while its process descriptor is still on the dead
queue and registered in the kqueue. When the child later exits, the
NOTE_EXIT handler dereferences the freed filed (use-after-free) and
never closes the process descriptor, leaving the pipe child as a
persistent zombie.
Capture whether the filed is a pipe with an active process descriptor
before calling close_filed(), and defer the free in that case so the
NOTE_EXIT handler can reap the child and free the filed.
Reviewed by: markj
Fixes: 95381c0139d6 (syslogd: Use process descriptors)
Differential Revision: https://reviews.freebsd.org/D59319
(cherry picked from commit 1a669b66ddb4748c24116e32dcb51eabaf4859ed)
