[fuzzer][test-only] Bump runs for reduce_inputs.test unseeded run (#169641)
I have seen a failure whereby the fuzzer failed to reach the expected
input and thus failed the test.
This patch bumps the max executions to 10,000,000 in order to give the
fuzzer a better chance of reaching the expected input. Most runs
complete successfully, so I do not see this adding test time in the
general case; I believe it's a fair tradeoff for the unlucky seed to run
for longer if it reduces the noise from false positives. Note, this
updates a different `RUN:` to
https://github.com/llvm/llvm-project/pull/165402.
rdar://162122184
NAS-138835 / 26.04 / Fix container attachment delegate (#17774)
## Problem
`container.stop` is a job now whereas in the attachment delegate we are
not treating it as one which can mean that when we want to have it
stopped, we will not wait for it to stop which can cause further issues
during the attachment delegate execution flow.
## Solution
Make sure `container.stop` gets treated as a job and is properly stopped
in attachment delegate when called.
NAS-138837 / 26.04 / Fix mountpoint issue for containers on importing pools (#17776)
## Problem
When importing a pool, if the mountpoint of container dataset is already
correct - we were falling through `inherit` block where system will
actually change it by adding it to `to_inherit` list.
## Solution
In the event when container dataset is already correct when a pool is
imported, we do not want to do anything in that case.
[llvm-c] Deprecate functions working on the global context (#163979)
One of the most common mistakes when working with the LLVM C API is to
mix functions that work on the global context and those that work on an
explicit context. This often results in seemingly nonsensical errors
because types from different contexts are mixed.
We have considered the APIs working on the global context to be obsolete
for a long time already, and do not add any new APIs using the global
context. However, the fact that these still exist (and have shorter
names) continues to cause issues.
This PR proposes to deprecate these APIs, with intent to remove them at
some point in the future.
RFC:
https://discourse.llvm.org/t/rfc-deprecate-c-api-functions-using-the-global-context/88639
mvc: introduce defaultConfig property for AppConfig
Related to testing there is a side effect from snatching the
default config.xml if no other configuration was found. We
want the tests to be independent of runtime so this is a first
step towards it. While here replace other uses of the default
file acquire and almost completely fix the permission issue
on default bootstrap.
Setting working directory after fork means there is a race with
pane_current_path (especially on platforms with systemd which have to
take time to do some additional faffing around). To avoid this, change
it before fork and back in the parent afterwards. GitHub issue 4719.
[IR] Add ImplicitTrunc argument to ConstantInt::get() (#170865)
Add an ImplicitTrunc argument to ConstantInt::get(), which allows
controlling whether implicit truncation of the value is permitted.
This argument currently defaults to true, but will be switched to false
in the future to guard against signed/unsigned confusion, similar to
what has already happened for APInt.
The argument gives an opt-out for cases where the truncation is
intended. The patch contains one illustrative example where this
happens.
[clang-tidy][NFC] Add empty '.clang-tidy' file in tests dir to silent warnings in IDE (#171029)
When working on tests, `clangd` with option `--clang-tidy` will report
warnings from
[root](https://github.com/llvm/llvm-project/blob/main/.clang-tidy)
clang-tidy config.
I believe these warnings serve no purpose in tests, so we better disable
them to silent warnings in IDE.
www/edbrowse: initial import
Edbrowse is a combination editor, browser, and mail client that is 100%
text based. The interface is similar to /bin/ed, though there are many
more features, such as editing multiple files simultaneously, and
rendering html.
[RISCV] Re-generate rvp-ext-rv32.ll after #170399. NFC
Some instructions got renamed by #170399, but new tests cases were
added after that PR was created.
py-pdf: updated to 6.4.1
6.4.1, 2025-12-07
Performance Improvements (PI)
- Optimize loop for layout mode text extraction
Bug Fixes (BUG)
- Do not fail on choice field without /Opt key
Documentation (DOC)
- Document possible issues with merge_page and clipping
- Add some notes about library security
Maintenance (MAINT)
- Use CORE_FONT_METRICS for widths where possible
