Ideally these should be rewritten to avoid relying on setting the defaults, but for now an effort is done to make sure that the initial value is restored after testing, and that
these tests don't run in parallel with other tests.
Signed-off-by: Ravi Nadahar <nadahar@rediffmail.com>
* Upgrade Karaf to 4.4.9
Upgrade Karaf from 4.4.8 to 4.4.9.
This includes upgrades for the following libraries:
* jetty from 9.4.57.v20241219 to 9.4.58.v20250814
* pax-web from 8.33 to 8.34
* asm from 9.8 to 9.9
* bouncycastle/bcprov from 1.81 to 1.83
* classgraph from 4.8.180 to 4.8.184
* commons-cli from 1.9.0 to 1.10.0
* commons-io from 2.20.0 to 2.21.0
* commons-lang3 from 3.18.0 to 3.20.0
* cxf from 3.6.8 3.6.9
* guava from 33.4.8-jre to 33.5.0-jre
* jackson-annotations from 2.19.2 to 2.20
* jackson from 2.19.2 to 2.20.1
* jna from 5.17.0 to 5.18.1
* ws.xmlschema from 2.3.1 to 2.3.2
* xbean from 4.27 to 4.28
* xtext/xtend from 2.40.0 to 2.41.0
Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
* New translations automation.properties (Czech)
* New translations messages.properties (Czech)
* New translations messages.properties (Dutch)
* New translations automation.properties (Dutch)
* New translations defaultsystemchannels.properties (Czech)
* New translations addons.properties (Czech)
Bundle cannot contain the actor separator ($) or the
delegation separator (=>), and actor cannot contain the delegation
separator.
Also rename the package parameter to bundle, to make it clearer they
shouldn't be any more specific than the full bundle package name.
Signed-off-by: Cody Cutrer <cody@cutrer.us>
* Refactor websocket concurrency handling
* Modify web socket buffering logic to ensure FIFO and avoid blocking the logger thread
* Use a dedicated executor that is guaranteed not to log anything
* Logging tweak
Signed-off-by: Ravi Nadahar <nadahar@rediffmail.com>
Some of the SDDP tasks are long-running by design, the background scan task in particular runs indefinitely (until interrupted). This clashes with the idea in #4969, and perhaps with the envisioned use of OH's shared thread pools in general, in that pools are small and tasks are expected to be short-lived. When setting logging to DEBUG, the log will be constantly "spammed" with complaints about the SDDP discovery task taking more than 5 seconds, which it is in fact designed to do.
Signed-off-by: Ravi Nadahar <nadahar@rediffmail.com>
* [rest-api]: Change error code 500 to 400
Change the response code of the rest api when submitting invalid
parameters.
Signed-off-by: Zhivka Dimova <zhivka.dimova@myforest.net>
* Remove double localization of discovery results
Localization of discovery results requires a bundle from which to acquire the translations. When bindings implement AbstractDiscoveryService themselves, the bundle is resolved using the class of the implementation. For "sub discovery services" where bindings are "participants", this doesn't work, because the implementing class is the "sub discovery service" itself, not the binding, which means that the resolved bundle doesn't have any translations. This has been solved by doing an extra round of localization in the "sub discovery service" (using the correct bundle) before passing the DiscoveryResult on to AbstractDiscoveryService, which will attempt localization again, with the wrong bundle, but since no translations are found in this bundle, it has no other consequences than being wasteful.
This solves the problem by adding a second thingDiscovered() method to AbstractDiscoveryService, which accepts a bundle as a second argument. That way, "sub discovery services" can resolve the correct bundle using the participant class, and pass on the correct bundle, avoiding the "double localization".
In addition, a new factory method is added to DiscoveryResultBuilder that allows initializing a new builder from an existing DiscoveryResult instance, so that this doesn't have to be done in the localization method itself.
Signed-off-by: Ravi Nadahar <nadahar@rediffmail.com>
Automatically marks Home Assistant addon for installation if the
MQTT binding is marked for installation, and Home Assistant things
exist
Signed-off-by: Cody Cutrer <cody@cutrer.us>
Isolated DSL/YAML models are models that do not fill the things/items/... registries when they are loaded.
They are used as temporary models for particular features.
These models have a particular prefix in their names to distinguish them.
It was "tmp_" before, it is now "___tmp_".
The risk that a user names one of its file with such prefix is reduced.
If a DSL file with prefix "___tmp_" is by the way used by a user, this file is ignored and a message is now logged to inform the user.
Closed#5134
Change pattern for isolated model name
tmp_DSL_model_<N>.items => ___tmp_model_<N>.items
tmp_YAML_model_<N>.yaml => ___tmp_model_<N>.yaml
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
* [DSL/YAML generator] Consider item pattern formatter even without label
Items without label but with a formatter are now properly considered when generating DSL and YAML syntax.
Example: Number SceneItem "[MAP(scene.map):%s]"
Bug was reported on the community forum.
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
* Fix typos discovered by Copilot
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
---------
Signed-off-by: Laurent Garnier <lg.hc@free.fr>