i am thinking about upgrading my mariadb production servers to 10.4 and i would like to ask you if you have any troubles with specific minor versions on 10.4.
So have you troubles with any version? Or what version are you running without any problems?
I would suggest using the latest stable release of MariaDB, that is version 10.4.12, which was released on January 2020.
You will benefit the cumulative fixes of all previous subversions of 10.4 - the first stable subversion of 10.4 was 10.4.6 (released in June 2019), so lot of work has been put into stabilizing it already.
Please note that version 10.5 is on its way too: alpha released 10.5.0 happened in December 2019; but as of today there is still no stable version available (10.5.1 - Beta, was released this month), so if you want something bullet-proof it is too early.
Of course, as always, you should install and test this in QA environment before moving to Production so you can ensure that everything works smoothly in your ecosystem.
Related
I need to get acquainted specifically with elm 0.16.XX because some project I am working on is using it, and long story short,e.g. the version cannot be changed. Also, as you guys know there is a significant change between 0.16 and later elm versions. I am doing an online video course that has the 0.16.XX version but when I install elm, it naturally installs the latest version. How can I install the older versions?
The info I see online says to just change in elm.json, the version numbers of dependencies you need, but the problem is that the names of the dependencies have also changed. e.g in a basic hello world project,
0.16.xx
"elm-lang/core": 5.1.1, "elm-lang/html": 2.0.0, "elm-lang/virtual dom": 2.0.4
as opposed to modern elm
"elm/core": 1.0.5, "elm/html": 1.0.0, "elm/virtual-dom": 1.0.3
So how do I go about installing older elm i.e 0.16.XX. Any help is appreciated.
In theory, you could download the source code zip and try to build from sources but I remember people having a lot of trouble with the particular Haskell dependencies.
If the app is an Html based app that used evancz/start-app you might have some luck by first upgrading to 0.17.1. Take a look at https://github.com/elm-lang/elm-platform/blob/master/upgrade-docs/0.17.md
You might be able to install 0.17.1 with npm i -D elm#0.17.1.
elm.json is available only to 0.19 and 0.19.1 projects. The versions before that used elm-package.json
You can download Elm 0.16 installers for Windows and Mac Elm from the official releases.
https://github.com/elm/compiler/releases/tag/0.16.0
But I have no idea if installing the dependencies still works.
So maybe you'll need to incrementally upgrade your code, see https://github.com/elm-lang/elm-platform/tree/master/upgrade-docs
If that is too complicated, maybe you can ask in the Elm slack if someone can upgrade the code for you? E.g. with a small freelancer contract?
When I try to generate unit tests in GNAT 2020 Community Edition (Windows 10 64 bit), I get an error on missing gnattest tool: could not locate gnattest.
Same happens on Ubuntu 20.04 (in WSL) with package gnat-10: could not locate x86_64-linux-gnu-gnattest-10.
Is GNATtest not part of GNAT 2020 Community Edition, as shown on AdaCores website (https://www.adacore.com/gnatpro/comparison)?
Yes in 2020 Community Edition gnattest is not included. Main reason: gnattest is tool based on library ASIS which is no longer maintained. AdaCore is moving towards libadalang library and for now gnattest is a victim of these changes. It will back soon or later to Community Edition (when it will be rewritten to use libadalang). Source: I was hit by this same problem and I got this answer from AdaCore :)
At this moment, you can download source package asis-2019-20190517-18AB5-src.tar.gz from previous version of GNAT and compile it by self. At least for me, it works.
AdaCore are moving away from ASIS to their own libadalang technology, and GNAT CE 2020 doesn’t include ASIS.
The ASIS-based applications in GNAT CE 2019 are
gnat2xml
gnat2xsd
gnatcheck
gnatelim
gnatmetric *
gnatpp *
gnatstub *
gnattest
of which only the ones marked with an asterisk are in GNAT CE 2020 (for macOS, at any rate).
If you do go with #thindil’s answer, it’d be best to install the ASIS tools in their own directory, so as to avoid stomping on gnatpp etc.
For info, gnatelim is missing because - for targets using the GNU linker - -ffunction-sections, -fdata-sections, and -gc-sections do the equivalent job
On Ubuntu you can just install asis applications with : sudo apt install asis-programs
I would like to know how to get the latest version of Firebase. How would I select from latest, beta, or stable versions?
As of now, I believe the latest Firebase is version 3.5.1. I am not even sure.
Any help or suggestions is appreciated.
The latest Firebase releases, for all platforms, are listed in the release notes, which can be found here.
If you are using the NPM-distributed Firebase, you can run the following command to see the latest version:
npm view firebase version dist-tags
Which effects the following output:
version = '3.5.1'
dist-tags =
{ latest: '3.5.1',
'1.2.0-beta.1-0': '1.2.0-beta.1-0',
'1.2.0-beta.2': '1.2.0-beta.2',
'1.2.0-beta.3': '1.2.0-beta.3' }
Note that dist-tags includes the latest, stable release and some very old betas. As mentioned in the comments, the latest, stable release is the only Firebase release. If beta or next versions were to be released, they would typically be listed in the dist-tags.
I've run these commands:
ld_add('/path/datasets/dbpedia/2015-04/dbpedia_2015-04.owl', 'http://dbpedia.org/resource/classes#');
rdf_loader_run();
ld_dir_all('/path/datasets/dbpedia/2015-04/importedGraphs/dbpedia.org', '*.*', 'http://dbpedia.org');
That all ran successfully, but then I ran:
rdf_loader_run();
It's been 48 hours on a CoreI7 machine with 24GB ram, Virtuoso server is not using any CPU, and it doesn't respond to queries such as:
select * from DB.DBA.LOAD_LIST;
...in another instances of isql-vt. The size of files in /var/lib/virtuoso-opensource-6.1/db/ are not increasing.
The problem was I was using an old version of virtuoso, by upgrading to 7.2 as suggested in comments it solved. I didn't have this problem on my macbook, so seems that while homebrew installs latest version by default, apt-get doesn't do so in Ubuntu and you need to install the latest version.
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.