I'm trying to build StreamSets Data Collector with source codes by following the steps in public Streamsets git repository (SDC Public github link).
Following picture is the screenshot of error.
Error message I've got when I tried to build StreamSets with source code
I've done the whole tasks that I should do before building SDC which is written on github build.md page, and following softwares are installed successfully with correct version.
JDK : v1.8
Git : v2.18.0
Maven : v3.5.4
Docker : v18.03.1.ce
Node : v0.10.32
grunt-cli : installed(v1.4.0)
bower : v1.8.2
go : v1.9.2 (gvm used)
gradle : v4.2
I've got the same error message about more than two weeks, and it drives me really crazy. I need your help. Thank you.
It looks like the instructions for building Data Collector Edge in BUILD.md are incorrect. The correct command to build Edge and populate the local Maven repository with the artifacts is:
./gradlew clean dist publishToMavenLocal
I've opened SDC-9842 to fix this. It should be updated on GitHub soon.
Related
I have cloned the Wazuh-Kibana-app source code from https://github.com/wazuh/wazuh-kibana-app
I have made some changes in the styling. So, i am making build of the app by running npm run build but i am getting this error
Command "plugin-helpers" not found
I think it is because in package.json file, it gets like that "plugin-helpers": "node ../../scripts/plugin_helpers" as it is getting out of the directory. So how to resolve this issue?
The Wazuh Kibana plugin uses the Kibana plugin_helpers to build a distributable archive of the plugin, information on how to create a Kibana development installation which is capable of building the Wazuh plugin can be found here: https://github.com/wazuh/wazuh-kibana-app/wiki/Develop-new-features
There is also the option of building the Kibana plugin using the wazuh-packages tools as explained here: https://documentation.wazuh.com/current/development/packaging/generate-wazuh-kibana-app.html , however as of right now this only accepts branches from the official Wazuh plugin.
Let me know if you have any more questions!
I have built a site using Hugo from a template called uBlogger, pushed everything on GitHub and then I used Netlify to deploy the site.
On the deploy log, it says
Error: Error building site: TOCSS: failed to transform "css/db6b6c.scss" (text/x-scss): SCSS processing failed: file "stdin", line 1, col 6: Invalid CSS after "#id-1{": expected "}", was "<nil>}"
Honestly I have been trying to look for the file "db6b6c.csss", which doesn't exist in my project, and I haven't found any information online so I have no clue of what to do. Does that mean I have to go through all the files there is in my folder and look for "#id-1{" ?
Check first if this is similar to this thread, where:
the OP did not initially download the extended version of Hugo,
the OP, on Netlify, one user switched to Ubuntu Xenial 16.04 (default, instead of an older one), and everything worked.
Our development team implemented Pdfsharp in order to generate the pdf at website
they installed the pdfsharp package in a local environment with using this command at VisualStudio "Install-Package HtmlRenderer.PdfSharp -Version 1.5.0.5" it working fine
comes to production environment code is deployed through Azure DevOps CI/CD
when the build process creation we are implemented Nuget, NPM, and other steps.
now we added same line command in with .Net-CLI " add package HtmlRenderer.PdfSharp --version 1.5.0.5"-----> when I doing like it through the error message
Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code 1
Dotnet command failed with non-zero exit code on the following projects :
I tried to install a pdfsharp package directly in webapp (API) using PowerShell
but I don't have an idea about installing the pdfshap in backend server level is it the right way or not is still ??
Please see the overview on how to use packages.
In short, you only install/add the package to the project once. This modifies the project, and you save the modified csproj into source control. Then on the CI machine, you run dotnet restore on your solution (if your solution contains only SDK style projects, nuget restore otherwise).
And for future reference, telling us that dotnet.exe returned exit code 1 is insufficient to understand the problem. dotnet.exe's output will contain additional error information about why it failed.
I have a build pipeline configured for a Service Fabric solution on Azure DevOps like this:
Everything was fine until a few days ago when the build started failing on a particular build agent (private), with the following error (for a few projects):
C:\Program Files\dotnet\sdk\2.1.200\Sdks\Microsoft.NET.Sdk\build\Microsoft.PackageDependencyResolution.targets(327,5): Error : Assets file 'F:\Agent03\w\84\s\src\MyProject.Sam.Tiles.Domain\obj\project.assets.json' not found. Run a NuGet package restore to generate this file.
The failing task is the Build solution $(PathToSolution) one.
The weird thing is that the build fails when running on some agents but with others the build is fine.
Some details:
Use NuGet 4.x task started using NuGet v4.9.1 very recently, I think. I tried using v4.8.1 with no luck;
Most of the projects use the PackageReference format, but the .sfproj project uses the packages.config file
I tried using the dotnet restore task but there is an error when trying to restore the packages for the .sfproj project:
`Error : Unable to find the
'....\packages\Microsoft.VisualStudio.Azure.Fabric.MSBuild.1.6.7\build\Microsoft.VisualStudio.Azure.Fabric.Application.props'
file. Please restore the
'Microsoft.VisualStudio.Azure.Fabric.MSBuild' Nuget package
Any idea on what might be causing this issue?
Some of the projects use the PackageReference format but the .sfproj project uses the packages.config file.
I still don't understand why the build started failing, but I was able to find a workaround. Given that PackageReference is not yet supported in Service Fabric projects, my workaround was to use both restore tasks as follows:
My problem turned out to be a solution that didn't include all the necessary projects.
I have a master solution file that includes all my projects, and a number of smaller solution files with only some of the projects. The master solution built fine in Azure DevOps, but the partial solution failed.
I realized that the missing project.assets.json file belonged to a project that needed to be included in this failing solution.
Trevor's comment on 2/20 gave me the clue. You likely don't have the complete set of projects referenced by the solution. (ProjectReferences may go to other projects, which are not in the solution).
Here is why this crazy workaround (run dotnet.exe and nuget.exe restore tasks) worked:
dotnet restore will walk project references by default to ensure they are restored also.
--no-dependencies switch can turn that off.
nuget.exe restore has the opposite default, because we didn't want to break old users.
-recursive can turn this on.
The right solution is to make your solution contain all the projects.
-Rob Relyea
NuGet Client Team, Engineering Manager
i'm trying to build movie recommendation application using PredictionIO.
i have already using PredictionIO 0.11 on Docker, the issue
that when i run pio build --verbose it's showing:
no engine found. your build might have failed. aborting.
not sure where to puts the recommendation template files?.
any idea?
You need to be sure that you are in the current working directory of your engine I mean you have to execute your pio build --verbose command from the directory where your templates's engine.json file is placed . If this not solves your issue can you please paste the complete error along with template link.