I am trying to use the plug in provided for QR Code scanner for lower version of oracle apex which is 20.1.
When using same plugin with latest version (21.2 or 22.1) it works correctly.
But when using same plugin with lower version it gives error.
Link is below:
https://github.com/RonnyWeiss/APEX-QR-Code-Scanner
Same plugin with latest version
Check latest version image here
Same plugin with lower version giving error
Check lower version error image here
I want to use this plugin in to lower version of oracle apex. How can I do that?
Related
In one of our website we are using CKEditor version 4.5.4. After Penetration testing, upgrading the CKEditor version to the latest one is recommended.
Functionality point of view we don't want to change anything. So, to which version we should upgrade either to 4.20.0 or to version 5. The target is to remove vulnerabilities.
I have an Azure DevOps pipeline using a macos-latest image. That constantly fails when the image version is 20201212.1. And it works as expected with the image version 20210110.1.
Is there a way to select the image version in the pipeline?
When using Microsoft-hosted agents to run pipelines, typically it will automatically update the image to the latest release for use (generally updated weekly). And we can't specify the image version of the agents.
Currently the released latest image version of macOS agent (macOS X Catalina 10.15) is 20201212.1 (see here).
The image version 20210110.1 is Pre-release now (see here). Currently, this image version has not been deployed completely on Azure DevOps, and there may be few regions are be able to use this image version.
In your case,
That constantly fails when the image version is 20201212.1. And it works as expected with the image version 20210110.1.
What is the details of the error message in the output logs?
If the issue is caused by different versions of some software installed on the image, you can try to update or install the software with the versions you require. to view more details, you can reference here.
If the issue still exists after changing the software versions, I recommend that you can open an issue on the "actions/virtual-environments" repository for more help.
I just upgraded from SonarQube 6.1 to 6.7.7. For SonarJava, it automatically installed 4.15.0.12310 (it was 4.10.0.10260 before). In the Marketplace, when I hover over the available versions from 5.0-5.13, it says “Incompatible”. When I hover over 5.13.1+, it says “Requires system update”. What does it mean for it to be incompatible if it doesn’t require a system update?
I am seeing this with various other plugins as well, such as SonarPython, which had 1.8 automatically installed. I had to manually install 1.9.1 in order to get this bug fix (which is why I originally upgraded the server): https://community.sonarsource.com/t/python-s1481-code-smell-unused-local-variables-should-be-removed-false-positive-with-string-interpolation/8961
I could manually install newer versions of other plugins as well, but I don’t know if that’s safe.
I also can’t find an official plugin compatibility matrix, since this only shows 7.9+: https://docs.sonarqube.org/latest/instance-administration/plugin-version-matrix/
Incompatible means that the plugin does not work with the version of SonarQube you have installed.
An example of an incompatible plugin would be one where the plugin relied on an API that was removed in your current SonarQube version. You may be able to use that version of the plugin if you downgraded your SonarQube instance to a previous version.
Requires system update means you need to upgrade SonarQube in order to install the plugin.
For what it's worth, the states as described by the API documentation are:
Update status values are:
COMPATIBLE: plugin is compatible with current SonarQube instance.
INCOMPATIBLE: plugin is not compatible with current SonarQube instance.
REQUIRES_SYSTEM_UPGRADE: plugin requires SonarQube to be upgraded before being installed.
DEPS_REQUIRE_SYSTEM_UPGRADE: at least one plugin on which the plugin is dependent requires SonarQube to be upgraded.
I am using 5.6 version of sonar, want to upgrade to 6.7. Can I directly upgraded to 6.7 ?
I have 8-10 sonar projects hosted on a same instance of sonar server. I am not sure what would break after upgrade. I am thinking of following approach
Install (do not upgrade) a new version of sonar 6.7, this would run on the different port(s).
Create a copy of sonar database which I have with my older sonar version, attach that copy of DB to new installation of sonar (by updating the sonar configuration file).
Assuming everything works fine, retire the older version (sonar server & DB).
I am using dedicated database as SQL server.
Anybody tried this approach? does it work?
Atul
If you're using one of the supported databases, you can upgrade directly from 5.6 to 6.7.
Simply follow the Upgrade Guide - and make sure that you back up your DB first in case of troubles.
Before I upgraded Sonar 5.0 I used the internal org.codehaus.sonar:sonar-maven-plugin:4.3.2. After the upgrade I used the same plugin in version 5.0 but got the error
Failed to execute goal org.codehaus.sonar:sonar-maven-plugin:5.0:sonar (default-cli) on project at.biac.offer.pom: Please update sonar-maven-plugin to at least version 2.3
Then I switched to org.codehaus.mojo:sonar-maven-plugin:2.5 but now I get the following error
org.sonar.jpa.session.DatabaseException: Database schema must be updated [version/required=721/170]. Please browse to your sonar homepage.
Is there any way to fix this problem without loosing my analysis data so far?
Database upgrade is a normal step when doing an upgrade of the SonarQube server. You should not lose any data.