calendar.freebsd: add myself (khorben@)
This adds my date and place of birth to FreeBSD's calendar file, so I
can let the system(tm) remind me when that counter increments.
Confirmed to be working with the following command:
```
$ calendar -f usr.bin/calendar/calendars/calendar.freebsd -t 18.08
Aug 18 Pierre Pronchery <khorben at FreeBSD.org> born in Nantes, France, 1982
[...]
```
Reviewed by: philip (mentor)
Approved by: philip (mentor)
Differential Revision: https://reviews.freebsd.org/D55825
sysutils/logstash7: Update 7.17.11 => 7.17.29, deprecate
Release Notes:
https://www.elastic.co/guide/en/logstash/7.17/releasenotes.html
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download
due to the HTTP error "Forbidden 403".
- Deprecate with date 2026-06-30 due to 7.x reached EoL on 15 Jan 2026.
- Limit JAVA_VERSION to supported 17, 11 and 8.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Add possibility to use custom user/group.
- Merge CHMODs.
- Fix white characters and remove unnecessary empty lines.
- Remove unnecessary MKDIR.
PR: 293746
[4 lines not shown]
textproc/elasticsearch7: Update 7.17.11 => 7.17.29, deprecate
Release Notes:
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/es-release-notes.html
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download
due to the HTTP error "Forbidden 403".
- Deprecate with date 2026-06-30 due to 7.x reached EoL on 15 Jan 2026.
- Limit JAVA_VERSION to supported 21, 17, 11 and 8.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Fix warnings from portclippy.
- Fix possibility to use custom user/group.
- Remove unnecessary ".include <bsd.port.options.mk>" and variable SIGAR_ARCH.
- Merge MKDIRs, INSTALL_SCRIPTs, INSTALL_DATAs.
PR: 293746
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
[3 lines not shown]
textproc/elasticsearch7: Update 7.17.11 => 7.17.29, deprecate
Release Notes:
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/es-release-notes.html
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download
due to the HTTP error "Forbidden 403".
- Deprecate with date 2026-06-30 due to 7.x reached EoL on 15 Jan 2026.
- Limit JAVA_VERSION to supported 21, 17, 11 and 8.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Fix warnings from portclippy.
- Fix possibility to use custom user/group.
- Remove unnecessary ".include <bsd.port.options.mk>" and variable SIGAR_ARCH.
- Merge MKDIRs, INSTALL_SCRIPTs, INSTALL_DATAs.
PR: 293746
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
MFH: 2026Q1
sysutils/logstash7: Update 7.17.11 => 7.17.29, deprecate
Release Notes:
https://www.elastic.co/guide/en/logstash/7.17/releasenotes.html
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Add LOCAL/vvd/elastic to MASTER_SITES for those who can't download
due to the HTTP error "Forbidden 403".
- Deprecate with date 2026-06-30 due to 7.x reached EoL on 15 Jan 2026.
- Limit JAVA_VERSION to supported 17, 11 and 8.
- Parametrize "logstash" with "${PORTNAME}".
- Adjust CONFLICTS.
- Add possibility to use custom user/group.
- Merge CHMODs.
- Fix white characters and remove unnecessary empty lines.
- Remove unnecessary MKDIR.
PR: 293746
[2 lines not shown]
Fix KeyError in alert service test error handler
The error handler in alertservice.test referenced data["type"] but type
is nested under data["attributes"]["type"]. This caused a KeyError that
replaced the original exception, preventing the real send() failure from
being logged.
databases/pgvector: Update from 0.8.1 to 0.8.2
Changelog:
* Fixed buffer overflow with parallel HNSW index build - more info
* Improved install target on Windows
* Fixed Index Searches in EXPLAIN output for Postgres 18
Taken from:
https://github.com/pgvector/pgvector/blob/master/CHANGELOG.md
Sponsored by: OTTRIA
[mlir][test] Fix UNREACHABLE in TestInlinerInterface for multi-block inlining (#186266)
When the MLIR inliner inlines a callable region that has more than one
block, it calls `handleTerminator(op, Block *newDest)` for the
terminator of every inlined block. `TestInlinerInterface` only
implemented the single-block variant (`handleTerminator(op,
ValueRange)`), so the default `llvm_unreachable` was hit when inlining a
`test.functional_region_op` whose body contained multiple blocks (e.g.
an explicit `cf.br` jump to a successor block whose terminator was
`test.return`).
Fix: add the missing `handleTerminator(op, Block *)` override to
`TestInlinerInterface`. Mirror the pattern used by
`FuncDialectInlinerExtension`: if the terminator is a `TestReturnOp`,
replace it with a `cf.br` to `newDest` carrying the return operands. Any
other terminator (e.g. `cf.br` for intra-region branches) is left
untouched — the existing `ControlFlowInlinerInterface` no-op already
handles those correctly.
[5 lines not shown]
Fix the send --exclude option to work with encryption
When using --exclude, filtering needs to take place in two places:
in zfs_main.c via the callback previously added to support the
options, and in libzfs_sendrecv.c because it generates the nvlist
during a first pass, and that results in it complaining if the
excluded dataset is not available for sending. (eg, excluding an
encrypted dataset so you don't have to use --raw wouldn't work,
because the first pass would look at the dataset and decide you
couldn't use it.) Add send --exclude tests, including one that tests
excluding an encrypted hierarchy.
Reviewed-by: Allan Jude <allan at klarasystems.com>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: Sean Eric Fagan <sef at kithrup.ie>
Closes #18278
Fix SNMP trap alerts failing to load TRUENAS-MIB
Commit 6a01cb9b removed the pre-compiled TRUENAS-MIB.py from
/usr/local/share/pysnmp/mibs/, but the SNMP trap alert service still
expected to load the MIB as a pre-compiled .py file from that path.
Replace with pySMI's addMibCompiler to compile the ASN.1 .txt MIB source
on-the-fly instead.
zstream: add a drop_record subcommand
It can be used to drop extraneous records in a send stream caused by a
corrupt dataset, as in issue #18239.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: Alan Somers <asomers at gmail.com>
Sponsored by: ConnectWise
Closes #18275
libzfs: scrub: only include start and end nv pairs if needed for scrub
This patch addresses running `zpool scrub <pool>` with ZFS 2.4 userspace
while the loaded kernel module is still 2.3, failing with:
```
cannot scrub <pool>: the loaded zfs module does not support an option
for this operation. A reboot may be required to enable this option.
```
Checking for the source of the message via `strace` showed the scrub
ioctl failing and setting errno to ZFS_ERR_IOC_ARG_UNAVAIL[0]. With
that and the comments in `module/zfs/zfs_ioctl.c`[1] commit: 894edd084
seemed like a likely cause for the backward incompatibility.
The corresponding kernelspace code in `module/zfs/zfs_ioctl.c` defaults
to a setting of 0 if either parameter is not set, so not providing the
nvpairs in case both are 0 should not make a semantic difference.
Tested by:
[19 lines not shown]
[libc] Add missing iswdigit to wctype.yaml and Windows entrypoints (#186023)
`iswdigit` was implemented
(https://github.com/llvm/llvm-project/pull/181635) but not declared in
the generated wctype.h (wctype.yaml) and was missing from the Windows
config entrypoints.
This pr declares iswdigit in wctype.h and enables it for the Windows
config.
also is part of https://github.com/llvm/llvm-project/issues/185136.
[SampleProfile] Skip counting mismatched weak symbols during profile loading (#185514)
Weak symbols may be overridden during linking, and this may cause
profile mismatch when compiling the weak symbols, while the profile was
created based on the overriding function. Skip counting the weak symbol
while checking the mismatched function profiles to avoid false alarm on
rejecting legit profiles.
[acc] Introduce ACCRoutineLowering for `acc routine` specialization (#186243)
This pass handles `acc routine` directive by creating specialized
functions with appropriate parallelism information that can be used for
eventual creation of device function.
For each acc.routine that is not bound by name, the pass creates a new
function (the "device" copy) whose body is a single acc.compute_region
containing a clone of the original (host) function body. Parallelism is
expressed by one acc.par_width derived from the routine's clauses (seq,
vector, worker, gang). The device copy created is simply a staging place
for eventual move to device module level function.
---------
Co-authored-by: Delaram Talaashrafi <dtalaashrafi at nvidia.com>
[VPlan] Account for any-of costs in legacy cost model
Some VPlan transforms, like vectorizing fmin without fast-math,
introduce AnyOfs, which have costs assigned in the VPlan-based cost
model, but not the legacy cost model. Account for their cost like done
for other similar VPInstrctions, like EVL.
Fixes https://github.com/llvm/llvm-project/issues/185867.
[Clang] Check sanitizer ignorelist for divrem overflow (#185721)
Instrumentation emitted for overflow by division was not checking with the sanitizer case list's type entries.
The original type-based ignorelist support (#107332) added `isTypeIgnoredBySanitizer` calls to `CanElideOverflowCheck`, which covers `+`, `-`, `*`, `++`, `--`. However, division and remainder have a separate code path in `EmitUndefinedBehaviorIntegerDivAndRemCheck` that never calls `CanElideOverflowCheck` or checks the ignorelist directly.
Add a check so that the SCL is honored for the div/rem case.
[lldb] Unify logging for GetAttributeAddressRanges error (#186258)
Use the same format string in DWARFCompileUnit.cpp as we do everywhere
else to report the error from GetAttributeAddressRanges. I noticed the
inconsistency when looking at our system log:
```
2026-03-12 05:36:48.600914 -0700 0x2e66: DIE has no address range information
2026-03-12 05:36:48.600950 -0700 0x2e8c: DIE has no address range information
2026-03-12 05:36:48.601068 -0700 DIE(0x1dc2): DIE has no address range information
2026-03-12 05:36:48.631000 -0700 DIE(0x80f4): DIE has no address range information
```
Add the --file-layout (-f) option to zdb(8)
Displays the physical raidz block layout for a given file.
This leverages the internal vdev_raidz_map_alloc() function to find
the map of how the block data is laid out across the child disks.
The column entry for each row looks like:
+------------+
| D2 43 |
| 6020da |
+------------+
representing here the logical data column 2 that is 43 sectors high
starting at sector 0x6020da.
With -H, the output is a list of disks, LBAs, and block counts,
given in 512 byte block values.
Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
[4 lines not shown]
[lldb] Turn on OSC 9;4 graphical progress in supported terminals (#185541)
In #162162, I added support for OSC 9;4 graphical progress. I put it
behind the `show-progress` setting because I didn't have a reliable way
to detect whether the escape code was supported by the terminal.
Since then, more tools have added support for it, most notably Claude
Code and Homebrew. While I still don't have a good way to detect this,
there are a handful of known terminals that are easy enough to identify.
This PR toggles the default of `show-progress` to on again and puts
showing the progress behind a check for those known terminals (Windows
Terminal, ConEmu & Ghostty).
This means that if you're running in one of those, you'll get the visual
progress by default unless you set `show-progress` to off. The downside
is that if you're on an unrecognized terminal, you can't force it on any
longer by setting `show-progress` to on. I think that's a fair trade-off
as the setting wasn't really advertised and I doubt many people are
using that. As a workaround, they can set `OSC_PROGRESS` to spoof an
OSC-supporting terminal.
