Validate Gradle Wrapper / Validation (push) Waiting to runDetails
CI / Matrix Preparation (push) Waiting to runDetails
CI / ${{ matrix.name }} (push) Blocked by required conditionsDetails
CI / Error Prone (JDK 17) (push) Waiting to runDetails
Release Drafter / Update Release Draft (push) Waiting to runDetails
removeUnusedImports causes issues with parsing newer Java, and
google-java-format requires --add-exports when running with Java 17+
We'd better use OpenRewrite for imports.
Validate Gradle Wrapper / Validation (push) Has been cancelledDetails
CI / Matrix Preparation (push) Has been cancelledDetails
CI / Error Prone (JDK 17) (push) Has been cancelledDetails
Release Drafter / Update Release Draft (push) Has been cancelledDetails
CI / ${{ matrix.name }} (push) Has been cancelledDetails
* Prepare to use Java 17 as minimal version
* See #6219 Pattern Matching for instanceof uses (Java 14/16)
* See #6219 - Implicit Typing with var (Java 10)
* See #6219 - Using Switch Expressions / yield Keyword (Java 14)
* See #6219 - Using Text Blocks (Java 15)
* See #6219 - some tunning / formating style
* See #6219 - tunning code
* See #6219 - Update Java argline params / remove java 8 / 9 args/comments
* See #6219 - formating code
* Remove not standard options for Java 17
* See #6219 - refactor CompOper to an enum
* See #6219 - fix unnecessary yield usage in the switch expression
* See #6219 - Optimize the code, fix formatting issue
Unrecoverable keys after opening the keystore could be a consequence of
the key having a different password than the keystore itself.
This could cause some people to spend a lot of time figuring out what's
going on, so let's just give them a quick heads up of a potential
(common?) reason for this error.
This could be fixed by running "keytool -keypasswd".
Without this patch, whenever a KeyStore is used (for example for client
certificates) in CLI mode, there is a message that no password was
provided.
This was caused by the else of the condition being on the wrong if
statement, and can cause people to spend a lot of time trying to debug
why the key store won't work.
A thread group might start later than the test. When we calculate delays on the start time of
the test, we might get a stampede of samples run at the start of the thread group.
When we use the test start time via JMeterContextService#getTestStartTime,
we might create a storm of test samples at the beginning, when a setup thread group
made us wait.
By providing this new class, this message can be prevented:
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
Sometimes in CI the brotli request will be redirected first, so try to not show
those redirects in the sampler output. Maybe we can get that test to working again.
Vladimir Sitnikov
Mend Renovate
Milamber
Raul Almeida
Alioth Null
Raul Almeida
Anjanan
junyejiang
Clay Johnson
Gabriele Coletta
František Bílek
linvaux
Patrick Uiterwijk
Felix Schumacher
David Getzlaff