This sounds like QPyBind11 to me?
Mark
-Original Message-
From: Development On Behalf Of Cristián
Maureira-Fredes
Sent: 31 August 2022 23:33
To: development@qt-project.org
Subject: [EXTERNAL EMAIL] Re: [Development] Repository request:
playground/qtscrypt
On 8/31/22 21:33, Konrad Ro
On Thursday, 1 September 2022 06:28:55 -03 Volker Hilsheimer wrote:
> * stress tests for data races: if your test doesn’t expose any race
> conditions if you run with QThread::idealThreadCount threads, then it’s
> unlikely that it will expose races if you run with more threads. But with
> time shar
Hi!
We have released the Qt 6.4.0 Beta4. Like earlier you can get it via online
installer. Src packages are also available in the Qt Account and
download.qt.io. Delta to the beta3 attached. Please make sure you report all
findings in Jira. Please also make sure all Qt 6.4.0 blockers are visibl
Volker Hilsheimer (1 September 2022 11:28) wrote (inter alia):
> * hardcoded waiting times is an anti-pattern.
A good way to avoid them is to use the QTRY_*() family of macros, as
long as you can find something that shall become true by the time the
waiting is no longer needed.
Eddy.
Hi,
You may have seen the qsizetype patches we've been pushing over the last
months. This is to give my perspective on the issue and why I think it's
needed:
First off, while I made QStringView qsizetype'd, because it was designed
to take input from STL containers[1], I was not involved in the
Thanks for sharing that overview, Anna!
When I chased after failures of my integrations caused by flaky tests during
summer, I’ve seen a couple of patterns I think are worth keeping in mind when
investigating flaky tests, or when writing new tests:
* QTest::qWaitForWindowActive - very often, a
