[TableGen] Tweak whitespace printing in DAGISelMatcherEmitter to avoid trailing whitespace in output.
The main offender was the trailing space in EmitVBRValue, but there
were a few other issues.
[MLIR][Python] Refine the support of `RewritePatternSet.add` (#173874)
This patch includes the following changes:
- `RewritePatternSet.add` now accepts op name (e.g. `.add("arith.addi",
fn)`) besides op class (e.g. `.add(arith.AddIOp, fn)`)
- add a concrete signature and a more complete docstring to
`RewritePatternSet.add`.
plasma6-plasma-activities-stats: add version 6.5.2
The KActivitiesStats library provides a querying mechanism for the data
that the activity manager collects - which documents hae been opened by
which applications, and what documents have been linked to which activity.
The activity manager also keeps the score for each document which gets
higher when a particular document has been often accessed or kept open
for longer periods of time. This score is also available through the
querying mechanism.
qcoro: add version 0.12.0
QCoro provides the tools necessary to make easy use of C++20 coroutines with
Qt. The cornerstone of the library is `QCoro::Task<T>`, which represents an
executed coroutine and allows the result of the coroutine to be asynchronously
awaited by its caller. Additionally, QCoro provides a set of wrappers for
common Qt types, such as `QTimer`, `QNetworkReply`, `QDBusPendingCall`,
`QFuture` and others, that allow to `co_await` their asynchronous operations
directly.
Remove bug compatibility for implementations that don't support
rekeying. AFAIK this is only an ancient Sun SSH version.
If such an implementation tries to interoperate with OpenSSH, it
will eventually fail when the transport needs rekeying.
This is probably long enough to use it to download a modern SSH
implementation that lacks this problem :)
ok markus@ deraadt@
Enforce maximum packet/block limit during pre-authentication phase
OpenSSH doesn't support rekeying before authentication completes to
minimise pre-auth attack surface.
Given LoginGraceTime, MaxAuthTries and strict KEX, it would be
difficult to send enough data or packets before authentication
completes to reach a point where rekeying is required, but we'd
prefer it to be completely impossible.
So this applies the default volume/packet rekeying limits to the
pre-auth phase. If these limits are exceeded the connection will
simply be closed.
ok dtucker markus
