[libc++][test] Use loop with compare_exchange_weak calls (#185953)
On AIX, this test sometimes fails with error `Assertion failed: y ==
true`. The test assumes `compare_exchange_weak` should succeed on a
single call, however according to the standard:
> A weak compare-and-exchange operation may fail spuriously. That is,
even when the contents of memory referred to by expected and ptr are
equal, it may return false and store back to expected the same memory
contents that were originally there.
This spurious failure enables implementation of compare-and-exchange on
a broader class of machines, e.g., load-locked store-conditional
machines. A consequence of spurious failure is that nearly all uses of
weak compare-and-exchange will be in a loop.
[atomics.ref.ops]/27
textproc/py-elasticsearch5: Deprecate - 5.x reached EoL, last version was in 2018
In such cases, I usually update to the latest version in the branch
(5.5.2 => 5.5.5) and only then deprecate the port, but here there is no
point in this - this is a very old branch, the latest version of which
was released in 2018, no one in the tree depends on it, and the ports
have the latest version 9.3.0 in the port textproc/py-elasticsearch.
Deprecate with expiration date 2026-06-30.
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
[MLIR][Python] Refine the behavior of Python-defined dialect reloading (#186128)
This includes several changes:
- `Dialect.load(reload=False)` will fail if the dialect was already
loaded in a different context. To prevent the further program abortion.
- `Dialect.load(reload=True)` implies `replace=True` in
dialect/operation registering.
- `PyGlobals::registerDialectImpl` now has a parameter `replace`.
- `register_dialect` and `register_operation` is no longer exposed in
`mlir.dialects.ext`.
This should solve the registering problem found in writing transform
test cases by @rolfmorel.
textproc/kibana93: New port: Browser-based analytics and search interface to Elasticsearch 9.3.x
Release Notes:
https://www.elastic.co/docs/release-notes/kibana#kibana-9.3.1-release-notes
PR: 290979
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
textproc/kibana8: Port improvements that were made while creating ports of version 9.x
- Improved text in COMMENT, pkg-deinstall, pkg-message, pkg-descr.
- Parametrize kibana with ${PORTNAME} in CONFLICTS.
- Add possibility to run port with non-default user/group www.
- Fix indents in post-patch.
- Refresh patches.
PR: 290979
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
Add new ports committer (mce)
Steps for New Committers.
1. Add an Author Entity
2. Update the List of Developers and Contributors
3. Add a News Item
4. Add a PGP Key
Reviewed by: osa, fluffy (mentors)
Approved by: osa, fluffy (mentors)
Differential Revision: https://reviews.freebsd.org/D55853
Update to version 9.2.0167.
Changes:
- patch 9.2.0167: terminal: setting buftype=terminal may cause a crash
- patch 9.2.0166: Coverity warning for potential NULL dereference
- patch 9.2.0165: tests: perleval fails in the sandbox
- patch 9.2.0164: build error when XCLIPBOARD is not defined
- patch 9.2.0163: MS-Windows: Compile warning for unused variable
- patch 9.2.0162: tests: unnecessary CheckRunVimInTerminal in test_quickfix
- patch 9.2.0161: intro message disappears on startup in some terminals
- patch 9.2.0160: terminal DEC mode handling is overly complex
- patch 9.2.0159: Crash when reading quickfix line
- patch 9.2.0158: Visual highlighting might be incorrect
- patch 9.2.0157: Vim9: concatenation can be improved
- patch 9.2.0156: perleval() and rubyeval() ignore security settings
- patch 9.2.0155: filetype: ObjectScript are not recognized
- patch 9.2.0154: if_lua: runtime error with lua 5.5
- patch 9.2.0153: No support to act as a channel server
- patch 9.2.0152: concatenating strings is slow
[100 lines not shown]
