While setting up the dashboard widgets on SonarQube 5.6.6 to display results from OWASP Dependency Check & ZAP and Xanitizer I encounter the following error message:
An error occurred while trying to display the widget "xanitizer". Please contact the administrator.
I have SonarQube running on a Windows 2008 Server R2 as a test instance.
What I did so far:
Installed the relevant plugins
Configured the plugin POM file with Windows paths (like: C:\Program Files (x86)\Jenkins\workspace\ZAP-Scanning\reports)
Created a reports either by a Jenkins job (for OWASP stuff) or by Xanitizer app.
Pointed SonarQube to the absolute path of Xanitizer report file in SonarQube GIU
Created each a SonarQube project manually
Linked the projects to the corresponding widget
The result is always the error message you can find above.
As a workaround I contacted Steve Springet directly. He pointed me to some GitHub pages, which did not help.
As I am not a developer: Is there any tutorial that might help?
Implementing Checkmarx plugin took some minutes to have scan results displayed.
Apparently I got stuck somewhere in the sonar.property files or the bridge between Windows and Linux syntax...
If helpful I can share the property and POM files with you.
This was a bug in the Xanitizer plugin. It has been fixed with version 1.4.0 of the plugin.
Related
Our build pipeline has been working fine, producing and saving packages to our Azure DevOps artifact feed. Although, we recently started seeing a strange failure in Visual Studio 2019 when trying to upgrade one of the packages to the latest version per to the following screenshot:
As the screenshot depicts, the package version 1.0.1-preview4 does exist but the project is not upgraded to it and version 1.0.1-preview3 has to be picked up instead to upgrade! Any idea what the root cause of this issue is and how to address this problem?
I run into this issue quite frequently and it is caused by Caching. Clearing your Nuget Cache will resolve the issue. See this StackOverflow post:
Package is not found in the following primary source
Apart from cleaning the cache, also check if the version 1.0.1-preview4 is valid(unlisted or deleted?) in your list.
Then use the filter to locate the View of the 1.0.1-preview4 package. Determine the view it belongs to, #Local, #Prerelease or #Release. After that go feed settings=>Views to check the related permissions:
Make sure your local account has the permission to the View the 1.0.1-preview4 package belongs to.
I'm the administrator of a WebApp and I'm having an strange behavior while using continuous delivery. If I right click site project and choose Publish site works fine, but if I use VisualStudio.com Build and Release I have following problem:
As I said, if I publish site everything is ok. I used Kudu to check files after Release and Storage is at bin folder.
Here are some of configs:
And here are Build and Release results:
I would suggest you try adding assembly binding redirects for the Windows Azure StorageClient library.
Reference: http://robertgreiner.com/2012/12/could-not-load-file-or-assembly-microsoft-windows-azure-storage-client/
Also check this https://devnet.kentico.com/questions/windows-azure-storage-dll-version-mismatch link which has similar issue discussed and check if this helps.
Also try the below workaround
UnInstall-Package WindowsAzure.Storage
Install-Package Microsoft.Data.Services.Client -Version 5.6.0
Install-Package WindowsAzure.Storage
After researching a lot I found that WindowsAzure.Storage v9 is not compatible with WebJobs. I just downgrade to V8.1.1 and now is ok.
I'm working with IBM MobileFirst 7.1, and trying to get integration for ISAM working. So far I've been working with the sample application provided here, but I'm having issues with it when working with 7.1 MobileFirst client-side tools.
If I download and unzip the v3.5 integration package, and unzip the ISAMforMobileFirst test project, and I build it with the v7.0 CLI, it builds successfully. However, if I build it with the v7.1 CLI, I get an error like this:
Migrating project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630.
[Error:
BUILD FAILED
/Applications/IBM/MobileFirst-CLI-7.1/mobilefirst-cli/node_modules/generator-worklight-server/lib/build.xml:497: com.worklight.upgrader.UpgradeEngineException: FWLPL0019E: Migrating the ISAMforMobileFirst project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630 has failed because Cannot parse /Users/ferriera/Downloads/AmWorklightAdapter-3.5/sample/ISAMforMobileFirst/server/conf/authenticationConfig.xml
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:271)
at com.worklight.upgrader.ant.UpgraderTask.execute(UpgraderTask.java:100)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
A colleague also sees this exact error in MobileFirst Studio 7.1 (in Eclipse) so I'm guessing it's not a CLI-specific error.
I would assume that support for something has changed in authenticationConfig.xml in 7.1, and this hasn't been reflected in the migrator.
A few questions:
Is ISAM integration supported in 7.1?
Whilst I realise the sample application isn't technically supported in 7.1, if/since ISAM integration is, in theory it should be feasible to make it work. What's changed in authenticationConfig.xml syntax?
Edit: looks like the failure happens due to the following: <parameter name="embedded-pki-bridge-ca-p12-file-path" value="<file-path>"/> and more specifically: <file-path>.
Change it to the actual file path, and it will not fail importing.
Nothing in the authenticationConfig.xml file is about ISAM really; it's all declarations of realms, login modules, security tests...
There is a clear failure, and a PMR should be opened.
As for a local workaround, I've attempted to remove segments in the file that I thought might trigger it, but did not succeed to find a pattern that causes it...
I have installed magento test Automation framework in local machine as below reference PDF.
http://www.magentocommerce.com/images/uploads/download/MagentoTestAutomationFrameworkInstallationGuide.pdf
All the installation setup has completed as per the reference.
After that i have added my project to netbeans. When i try to add the project in netbeans it seems error.
Below is the error message, which is i got from netbeans.
magento\app\design\adminhtml\default\default\template\catalog\product\attribute\js.phtml
This is my first try of Magento test automation tools. i don't know what was went to wrong.
Any help my appreciation.
Perhaps you can try changing a bit the directory structure
From
magento\app\design\adminhtml\default\default\template\catalog\product\attribute\js.phtml
To
magento\app\design\adminhtml\default\template\catalog\product\attribute\js.phtml
In my experience, Magento directory structure changes across its versions.
I'm trying Windows Azure now.
I have been following instruction from
https://www.windowsazure.com/en-us/develop/java/java-home/download-the-windows-azure-sdk-for-java/
I'm running on eclipse helios, but when i try to install new software and enter url repository :http://dl.windowsazure.com/eclipse
Eclipse always timeout,
message on message box like bellow :
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Connection timed out: connect
How to solve this, i very need it to deploy my first app on Windows Azure platform
Help me to solve this, please
Now i try to runnning azure project on Cloud Azure, but why when i try to upload cspkg file and cscfg file, the process always timeout, whereas connection is running normally when i look on ping -t
this is message when i try upload on azure hosting service :
Uploading the selected package has failed, please verify your network connection and try again.
How to solve this issue ?
it's very strange error. >-<
I think there is some problem with your network connection as I have just tested the same download location and it does work perfectly fine as below:
As you can see below I am using http://dl.windowsazure.com/eclipse URL to download the Java specific Azure components:
After that once I select "Next", the following two components are listed to be installed in my machine:
Microsoft JDBC Drive 3.0 for SQL Server (This will work with SQL Azure)
Windows Azure Plugin for Eclipse with Java
I am sure that the problem is specific to your network connection so please have it corrected.
Yes, it's foolish of me, i forget to shutting down my proxy server on My compute.After i disable it,everything gonna be alright :D
Thanks
surely I haven't meet this situation before , but just for your additional information..
Have you follow this step on installing azure #eclipse? like .net version must be >= 3.5
here are some source link for your help http://www.windowsazure4e.org/download/
I haven’t worked with Windows Azure Java SDK. But the error message is complaining the file C:\Users\workspace\AzureFirst\emulatorTools\ResetEmulator.cmd cannot be found. It would be better if you can check whether the file exists. In addition, the call stack points out you’re using Windows Azure SDK 1.4. Please try to upgrade it to 1.6 to see whether it works fine. You can find SDK 1.6 on http://www.microsoft.com/en-us/download/details.aspx?id=28045. Please install WindowsAzureEmulator and WindowsAzureSDK. The WindowsAzureLibsForNet is not needed if you don’t want to use .NET.
Best Regards,
Ming Xu.