Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from apache:master #220

Open
wants to merge 869 commits into
base: master
Choose a base branch
from
Open

[pull] master from apache:master #220

wants to merge 869 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Aug 21, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Aug 21, 2021
vlsi and others added 29 commits June 16, 2023 08:39
…all the events

Previously, HttpRequestInterruptTest received no events because the
listener was cloned, however, the test assumed there were no events because
the sampling was interrupted.
… the most often used scenario

This is a follow-up to #678
Previously, CollectionProperty.normalizeCollection failed to create a copy
of the input collection, and it resulted in null value.

How we create ArrayList or LinkedHashSet instead.
…ccounts for unmodifiable collection in normalizeList
It enables automatic JDK provisioning (e.g. download), and it enables
using different JDKs for executing Gradle and for building JMeter

Java version can be specified when building with -PjdkVersion=11

You could use ./gradlew -q javaToolchains to list the detected toolchains.

See https://docs.gradle.org/8.0/userguide/toolchains.html#sec:consuming

Fixes #5986
…gain

Java sampler was inheriting "enabled" status from its config element
as internally, Java Sampler UI always creates a config element and merges it
to the java sampler.

The solution is to move "configureTestElement(sampler);" to the very end of
modifyTestElement so all the base properties are populated based on
the element properties rather than "config element" properties.

Ideally we should somehow limit "mergeIn", and we should refrain from merging
unexpected properties.

Fixes #6004
…itializing in the constructor

Previously LoopController initialized continue_forever=true in the constructor,
however, and ThreadGroup.setMainController flipped the value to false.

It caused inconsistency since non-GUI launch does not call ThreadGroup.setMainController.

Using default=true enables to treat "false" as non-standard, so =false is saved
t the jmx, and it gets loaded in non-GUI as well.

Fixes #6008
…load roundtrip

ProxyControl initialized collection properties with HashSet which caused
CollectionProperty.equals to return false.
CollectionProperty is normalized to ArrayList on save, so we should not pass
HashSet to the CollectionProperty in the first place.
linvaux and others added 30 commits September 19, 2024 08:06
update org.apache.jmeter.JMeter#startUdpDdaemon to org.apache.jmeter.JMeter#startUdpDaemon

Closes 6325
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.
It seems, that the env variable JAVA_HOME__x64 is not set
…ties

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.
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.
…roughputTimer

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.
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.
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".
delete "return" in a private void method
…e name `menuItem` for clarity and consistency.
Removed unnecessary space in  a link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.