I have installed Apache Karaf 4.0.2 and Hawtio 1.456. The installation of Hawtio worked fine. But when I do bundle:list I see the "hawtio :: Karaf terminal plugin" in a failure state. However the hawtio functionality seems to be working.
Is it an incompatibility issue?
The terminal plugin has not yet been migrated to karaf 3.x/4.x as they changed the apis in karaf in a breaking way.
They did the same for the logger, which we had to do a fair amount of code to get working again.
So wait for a future release of hawtio where we have migrated the terminal plugin.
And hopefully the karaf guys dont break more stuff in future releases.
I logged a ticket: https://github.com/hawtio/hawtio/issues/2028
Related
There seems to be no proper documentation about upgrading airflow. The Upgrading Airflow to a newer version page only talks about upgrading the database. So what is the proper way of upgrading airflow?
Is it just upgrading the python packages to the newest versions? Or should I use the same venv and install the newer airflow version completely from scratch? Or is it something else altogether?
I'm guessing doing the database upgrade would be the final step followed by one of these steps.
I was also struggling with upgrading airflow for minor versions and didn't feel like I found a good answer in the docs. I think I have the right approach after looking back at how I installed airflow in the first place.
If you followed the guide to run airflow locally you'll want to change the value for AIRFLOW_VERSION in the commands to your desired version.
If you followed the guide to run airflow on docker, then you'll want to fetch the latest docker-compose.yaml. The command on the site always has the latest version. Then re-run docker compose up.
You can confirm you have the right version by running airflow version. I run airflow via docker so the docker steps work for me, I imagine the local steps should be about the same.
Adding to Vivian's answer -
I had installed airflow from PyPi and was upgrading from 2.2.4 to 2.3.0.
To upgrade airflow,
I installed the new version of airflow in the same virtual environment as 2.2.4 (using this).
Upgraded the database using airflow db upgrade. More details here.
You might have to manually upgrade providers using pip install packagename -U
After this, when I started Airflow, I got an error related to some missing conf. Airflow wanted the newest version of airflow.cfg, but I had the older version. To fix this,
Renamed my airflow.cfg to airflowbackup.cfg. This is done so that airflow will make a new airflow.cfg on start up when it sees that there is no config file.
Compared airflowbackup.cfg with the 2.2.4 config to find out all the fields I had changed.
Manually made those same changes in the newly made airflow.cfg
Prior to version 4.0.0 being released I had no problems with my app. I have been trying to update Firebase Tools since 3.19.3 was released and it will not work. It says that it updates without any errors but the tools are stuck on version 3.19.1. It is not updating.
After the release of 4.0.0 hosting no longer works. Cloud functions and Firestore are working without issue. I don't get any errors. It just doesn't work. I've been tying everything I can and searching all over forums for answers and nothing.
Hosting is not working. Static assets are not loading. It says that index.html cannot be found...but that is because there is no index.html because I am using express-handlebars templating engine. I have index.handlebars which was working fine before the release of firebase-tools version 4.0.0.
Still can't update firebase-tools to the latest version.
The issue was that I had firebase-tools installed in two different directories on my computer. The directory that was being updated was not the directory that my project was using. I'm still not sure how that happened but I uninstalled firebase and node and reinstalled them and that solved the problem.
To update firebase-tools, just run this command in the terminal:
curl -sL firebase.tools | upgrade=true bash
note: you must have curl installed.
Recently I need to deploy something on Karaf. I use Karaf 3.0.2 and event try 4.0.0M1. Both are not able to install war feature. Once I type feature:install war in console after Karaf start-up.
3.0.2 gives me:
Error executing command: Error resolving artifact org.apache.servicemix.specs:org.apache.servicemix.specs.activation-api-1.1:jar:2.2.0: Could not find artifact org.apache.servicemix.specs:org.apache.servicemix.specs.activation-api-1.1:jar:2.2.0
4.0.0M! gives me:
Erroe executing command: Error
I try to delete Maven and reinstall it. The issue is still there. It's not happened on other machine.
It's a strange issue. Could anyone meet it ever? Could anyone help me out?
As it works on the other machines, it's something on that certain machine.
Without much more details on the setup I'm using assumptions here.
1) No Network connection to the central repo
2) Using a Proxy wich isn't configured or configured wrong on the server
3) Using a nexus with credentials and those aren't configured or configured wrong
I encountered the same issue and it was because there were mirrors defined in my Maven settings.xml (due to usage in another project). After I commented them out I was able to install the karaf war deployer.
I really need some help with Plone. I am experiencing some issue upgrading from 4017 to 4018.
All the Plone websites say "The site configuration is outdated and needs to be upgraded."
When I press Upgrade I get the following error:
"Starting the migration from version: 4017
End of upgrade path, migration has finished
The upgrade path did NOT reach current version
Migration has failed"
I was really hoping someone could help me sort out this issue and also help me get to the latest stable build of Plone 4.1.
Thanks.
This happens when there is a discrepancy between the current Plone setup profile version number and the upgrade steps final version number. Because there is no step from 4017 to 4018 you get this error message.
This is not necessarily a problem. Your upgrade to version 4017 worked without a hitch. What exact Plone version are you upgrading to, 4.0.9? It may be worth reporting this as a (low priority) bug, but I doubt there is anything there to prevent you from using your site.
To illustrate, I see this all the time when using the latest development version of the Products.CMFPlone package, because that'll be one version 'tick' further than the latest release of the plone.app.upgrade package can upgrade me to.
the app store botched its installation of Xcode 4.1 (it turned claimed it was 4.0 but the app store claimed 4.1 was installed). So I deleted the /Developer folder thinking this would let me reinstall a clean Xcode 4.1.
The app store still thinks Xcode 4.1 is installed and will not download or reinstall any version of Xcode. How do I force install Xcode 4.1?
Just to explain further...
The App Store download had actually worked
What you saw when you looked at Xcode was your old install, because you had not yet run the installer at that point.
Just find the "XCode installer" in your applications folder and run that to complete the install.
It caught me out too.
Do you have the application "Install Xcode" in your /Applications folder. That worked for me.
Deleting the Install Xcode app works for me - after that I have the opportunity to download that monster all over again
To make a clean installation of Xcode first completely uninstall the previous Xcode version:
From a Terminal window type:
$ sudo /Developer/Library/uninstall-devtools --mode=all
That process may take a while!
Then try your installation again.