-
-
Notifications
You must be signed in to change notification settings - Fork 422
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
Resolver error introduced with Karaf upgrade to 4.4.5 #4158
Comments
I don't think there is something missing in our repo. For some reason |
@J-N-K thanks for the feedback. I still cannot reproduce on S3998 on RPI, OpenJDK 17.0.10. Not sure what is different on my test system, i.e. why the problem does not show here. @J-N-K What is the functional impact of the issue? Do addons fail to reload? Do you need to restart OH? @wborn Any idea what is going wrong? |
Which version of |
@J-N-K how do you get those version numbers from? OH console? I just double-checked pom file of Karaf 4.4.5 uses 3.18.0. |
Include Java Version on the affected system is
My not affected development system has
But I don't think that makes a difference. |
No, the Karaf bundles should always be present in the distribution itself.
|
My system (not affected) runs on S3998,
Karaf bundles look similar as in the post above.
I tried to stop the service, do a |
I also don't experience the issue anymore with snapshot 4000 on
|
On snapshot 4004 the issue is back, restarting openHAB several times and cleaning cache several times did not solve the issue. However did re-installing the Z-Wave binding do the trick and fix the issue. |
I believe I got this error when, I started snapshot 4064. Does not occur after a restart. |
I have tried to analyze this a bit further, as it looks like it is impacting add-on installation, including the installation of the add-on finders on a random basis. The problem always appears when the following line is called: Line 202 in 03a9708
I changed the code here: Line 441 in 03a9708
removing FeaturesService.Option.NoAutoRefreshBundles and commented line:Line 202 in 03a9708
This should refresh the features immediately after install instead of a delayed refresh. I didn't see the error anymore, in my tests and didn't see any negative consequence. However, I know this was introduced by @J-N-K in #3049. Reading through the comments it looks like there were good reasons for that, but I don't know enough about Karaf to be the judge on this. |
Likely this is resolved by #4224 (and a duplicate of #4222). |
@kaikreuzer Is there anything that needs to be uploaded to our Maven repo?
Originally posted by @florian-h05 in #4133 (comment)
It only happens once for me after an update / cleaned cache.
Originally posted by @J-N-K in #4133 (comment)
The text was updated successfully, but these errors were encountered: