Pivotal .NetCore 3.1 dotnet-runtime Error During Deployment - .net-core

I want to deploy my project using Pivotal from Bamboo. During the deployment of my .NetCore 3.1 project, I'm getting the error "Unable to install dotnet-runtime: could not find a version of dotnet-runtime to install". The deployment stack is set to cflinuxfs3.
I've tried specifying dotnet runtime version (3.1 and 3.1.5) in .csproj file but it got the same error so I removed it.
I've also created a buildpack.yml file and specified the .netcore sdk version as 3.1.x in there.
I'm sharing the property group from csproj and the manifest.yml file.
-- Error Log --
Downloading app package...
Downloaded app package (6.4M)
-----> Dotnet-Core Buildpack version 2.3.12
-----> Supplying Dotnet Core
-----> Installing libunwind 1.4.0
Copy[/tmp/buildpacks/b7bd2a36eb284e204524c677d2dbbfa2/dependencies/a54cfafce3d2a14e4f96777d5fd471f4/libunwind_1.4.0_linux_noarch_cflinuxfs3_05e08b22.tgz]
using the default SDK
-----> Installing dotnet-sdk 3.1.301
Copy[/tmp/buildpacks/b7bd2a36eb284e204524c677d2dbbfa2/dependencies/b422801667458a262ba26a3117b93e4f/dotnet-sdk_3.1.301_linux_x64_any-stack_80a771e4.tar.xz]
-----> Installing dotnet-runtime 3.1.5
Copy[/tmp/buildpacks/b7bd2a36eb284e204524c677d2dbbfa2/dependencies/40b5a460524fe7f1795c876445349a31/dotnet-runtime_3.1.5_linux_x64_any-stack_1aa84612.tar.xz]
-----> Finalizing Dotnet Core
ERROR Unable to install dotnet-runtime: could not find a version of dotnet-runtime to install Failed to compile droplet: Failed to
run finalize script: exit status 12 Exit status 223 Cell
ffe536bc-374c-46b5-a620-e3366dab6b22 stopping instance
b71ecb48-0083-4fd1-8f59-3a77b05de0e0
Error staging application: App staging failed in the buildpack compile
phase
-- .csproj --
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp3.1</TargetFramework>
<ServerGarbageCollection>true</ServerGarbageCollection>
<ConcurrentGarbageCollection>true</ConcurrentGarbageCollection>
<IsTransformWebConfigDisabled>true</IsTransformWebConfigDisabled>
<GenerateDocumentationFile>true</GenerateDocumentationFile>
<NoWarn>$(NoWarn);1591</NoWarn>
</PropertyGroup>
-- manifest.yml --
---
applications:
- name: projectName
memory: 1G
timeout: 240
instances: 1
routes:
- route: routeAddress
services:
- ARCHITECTURE.SERVICES-TST.ServiceRegistry
- ProjectName.Redis
- ProjectName.Dynatrace
- ProjectName.ConfigServer
env:
DT_TAGS: ((appName)) ((dc))-((env))
TZ: country
ASPNETCORE_ENVIRONMENT: environmentName
SPRING_CLOUD_CONFIG_LABEL: configLabel

Ok, here's what is happening.
The code is looking at the RuntimeFrameworkVersion in your .csproj file.
When that is empty, it's going to look at the TargetFramework and attempt to find a substring match using the regex netcoreapp(.*).
It is expecting that to have a single match, but in your case it does not, so you get that error message: could not find a version of dotnet-runtime to install.
Based on your .csproj file, it seems like what you have should be OK though. I did a quick check and the regex works and returns the version.
You could try setting RuntimeFrameworkVersion which would take a slightly different code path and might work for you.
You are trying to perform a source-based deployment. You could try dotnet publish first followed by a Framework Dependent Deployment which again would force a different code path.
It might be that the buildpack isn't finding your file, but it's hard to say without more info.

Related

Dotnet test questions on errors

I am working on Azure pipelines, running on a Windows self-hosted agent, behind a firewall to run automated tests.
I would want to see the tests results and code coverage in the pipeline results in Azure. My build pipelines are working but I never saw yet the results of automated tests so I'm not sure of what to expect.
I run this in my pipeline:
- job: Test
steps:
- task: NuGetAuthenticate#0
- task: DotNetCoreCLI#2
inputs:
command: test
projects: 'src/***.Test.Core/*.csproj'
testRunTitle: '***Tests'
arguments: '--collect "Code coverage"'
publishTestResults: true
Here are extracts of the logs, with my questions and comments:
Initialization of proxies and general stuff
##[debug]Agent.ProxyUrl=http://***proxy.***.***:443
##[debug]Agent.ProxyBypassList=["***.***,localhost,127.0.0.1","***.***","localhost","127.0.0.1"]
##[debug]Agent.CAInfo=*:\***Certificates\***PKIG2PEM.txt
##[debug]Agent.ClientCert=undefined
##[debug]Agent.SkipCertValidation=undefined
##[debug]command=test
##[debug]projects=src/***.Test.Core/*.csproj
##[debug]arguments=--collect "Code coverage"
##[debug]publishWebProjects=true
##[debug]workingDirectory=*:\Agent\_work\24\s
##[debug]check path : *:\Agent\_work\_tasks\DotNetCoreCLI_5541a522-603c-47ad-91fc-a4b1d163081b\2.179.2\node_modules\packaging-common\module.json
##[debug]adding resource file: *:\Agent\_work\_tasks\DotNetCoreCLI_5541a522-603c-47ad-91fc-a4b1d163081b\2.179.2\node_modules\packaging-common\module.json
Not sure what is CHCP but tests are run, with errors I believe linked to firewall so I'd expect to see those errors in the tests results
[command]C:\Windows\system32\chcp.com 65001
##[debug]publishTestResults=true
##[debug]Agent.TempDirectory=*:\Agent\_work\_temp
##[debug]defaultRoot: '*:\Agent\_work\_temp'
##[debug]pattern: '**/*.trx'
Results File: E:\Agent\_work\_temp\***_***_2020-12-17_16_13_24.trx
Attachments:
*:\Agent\_work\_temp\d992768e-f36f-4558-9b52-f42fc7cd3c74\***_***_2020-12-17.16_13_16.coverage
Failed! - Failed: 29, Passed: 0, Skipped: 0, Total: 29, Duration: 3 s - OECD.Glue.Contacts.API.Test.Core.dll (netcoreapp3.1)
Errors when pushing the results, what means "Failed to get FF TestManagement.Server.UsePublishTestResultsLibInAgent Value." ?
##[debug]Exit code 1 received from tool 'C:\Program Files\dotnet\dotnet.exe'
##[debug]STDIO streams have closed for tool 'C:\Program Files\dotnet\dotnet.exe'
##[error]Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code 1
##[debug]Processed: ##vso[task.issue type=error;]Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code 1
##[debug]BuildConfiguration=undefined
##[debug]BuildPlatform=undefined
##[debug]testRunTitle=***Tests
##[debug]adjustedPattern: '*:\Agent\_work\_temp\**/*.trx'
##[debug]Failed to get FF TestManagement.Server.UsePublishTestResultsLibInAgent Value.
Unable to get the FF: TestManagement.Server.EnablePublishToTcmServiceDirectlyFromTask. Reason: One or more errors occurred. (Moved Temporarily)
Failed to get FF TestManagement.PTR.CalculateTestRunSummary, what is CalculateTestRunSummary ?
##[debug]Failed to get FF TestManagement.PTR.CalculateTestRunSummary Value.
##[debug]Reading test results from file '*:\Agent\_work\_temp\***_***_2020-12-17_16_13_24.trx'
##[debug]Processed: ##vso[results.publish type=VSTest;mergeResults=false;runTitle=GlueContactsTests;publishRunAttachments=true;resultFiles=*:\Agent\_work\_temp\*_***_2020-12-17_16_13_24.trx;testRunSystem=VSTS - dotnet;]
I wonder what to do with these warnings, I don't know much about Dotnet core and Nuget, my job is only the pipeline, not the underlying project. In project settings, I see .Net Core 3.1, I don't understand where to look to find if I use Nuget version < 5.7 and if this warning applies to me
##[warning].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) - Use global.json using an older sdk version(<=3) to build
##[debug]Processed: ##vso[task.issue type=warning;].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) Use global.json using an older sdk version(<=3) to build
##[debug]task result: Failed
Then I have this, publish test results ends with Moved Temporarily, I'm guessing this is because of firewall, still, I did setup the proxy and other calls to Azure seems to work, what could be the issue ?
##[error]Dotnet command failed with non-zero exit code on the following projects : *:\Agent\_work\24\s\src\***.Test.Core\***.Test.Core.csproj
##[debug]Processed: ##vso[task.issue type=error;]Dotnet command failed with non-zero exit code on the following projects : E:\Agent\_work\24\s\src\***.Test.Core\***.Test.Core.csproj
##[debug]Processed: ##vso[task.complete result=Failed;]Dotnet command failed with non-zero exit code on the following projects : E:\Agent\_work\24\s\src\***.Core\***.Test.Core.csproj
##[section]Async Command Start: Publish test results
##[warning]Failed to publish test results: Moved Temporarily
##[section]Async Command End: Publish test results
##[section]Finishing: DotNetCoreCLI
Thanks for any help, Claude
Update 1 ---------------------------------
Thank you.
I understood that my version of DotNet Core on the agent is not good,
the agent has version 5 while the project references version 3.1.
I added this task :
- task: UseDotNet#2
inputs:
packageType: 'sdk'
version: '3.1.x'
But I am behind a firewall, still I have these logs:
##[debug]agent.proxyurl=http://***proxy.***.***:443
##[debug]agent.proxyusername=undefined
##[debug]agent.proxypassword=undefined
##[debug]agent.proxybypasslist=["***.***,localhost,127.0.0.1","***.***","localhost","127.0.0.1"]
##[debug]agent.proxybypasslist=["***.***,localhost,127.0.0.1","***.***","localhost","127.0.0.1"]
##[debug]AZURE_HTTP_USER_AGENT=VSTS_c11775e3-cd05-4e03-abd2-35da98ef2f0f_build_164_0
Tool to install: .NET Core sdk version 3.1.x.
##[debug]task result: Failed
##[error]Failed to download or parse releases-index.json with error: {"code":"UNABLE_TO_GET_ISSUER_CERT_LOCALLY"}
Would it be best to install this version locally ? In that case, would I have to do something special so it uses the correct version ?
Update 2 ---------------------------------
Thanks for that link to a known issue. I noticed that issue doesn't mention an error I have: {"code":"UNABLE_TO_GET_ISSUER_CERT_LOCALLY"}
Can it be that the task tries to reach 'https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/3.1/releases.json' but can't as we are behind a firewall ??
I don't understand why it tries to install DotNet Core as it is already installed but I don't know much about DotNet Core, I am only trying to run automated tests.
My last test included:
- task: NuGetAuthenticate#0
displayName: 'Authenticate with NuGet'
- task: UseDotNet#2
inputs:
packageType: 'sdk'
version: '3.1.101'
installationPath: '$(Agent.ToolsDirectory)/dotnet'
- task: DotNetCoreCLI#2
inputs:
command: test
projects: 'src/myProject.Test.Core/*.csproj'
testRunTitle: 'myProject'
arguments: '--collect "Code coverage"'
publishTestResults: true
Logs contains:
##[debug]agent.proxyurl=http://proxy.myCie.com:443
##[debug]agent.proxyusername=undefined
##[debug]agent.proxypassword=undefined
##[debug]agent.proxybypasslist=["myCie.com,localhost,127.0.0.1","myCie.com","localhost","127.0.0.1"]
##[debug]agent.proxybypasslist=["myCie.com,localhost,127.0.0.1","myCie.com","localhost","127.0.0.1"]
##[debug]AZURE_HTTP_USER_AGENT=VSTS_xxx_build_173_0
Tool to install: .NET Core sdk version 3.1.101.
##[debug]task result: Failed
##[error]Failed to download or parse releases-index.json with error: {"code":"UNABLE_TO_GET_ISSUER_CERT_LOCALLY"}
##[debug]Processed: ##vso[task.issue type=error;]Failed to download or parse releases-index.json with error: {"code":"UNABLE_TO_GET_ISSUER_CERT_LOCALLY"}
##[section]Finishing: UseDotNet
Thanks for any help
I think this is similar to GitHub issue #10969. It has something to do with internal GitHub repo/url. This is because the version which we specify in the task is searched in releases-index file, which is accessible to public as well:
You could also check the releases-index.json
{
"channel-version": "3.1",
"latest-release": "3.1.10",
"latest-release-date": "2020-11-10",
"security": false,
"latest-runtime": "3.1.10",
"latest-sdk": "3.1.404",
"product": ".NET Core",
"support-phase": "lts",
"eol-date": "2022-12-03",
"releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/3.1/releases.json"
},
In this case, I would recommend you to reopen the Issue #10969.

Error staging application: App staging failed in the buildpack compile phase in HWC Buildpack

I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.

Azure Devops - dotnetcore build fails consistently - process failed to start

Am setting up a small project build, which is in .Net Core. dotnet build fails everytime with below log:
2019-10-03T21:31:54.5434435Z ##[section]Starting: dotnet build
2019-10-03T21:31:54.5559431Z ==============================================================================
2019-10-03T21:31:54.5559511Z Task : .NET Core
2019-10-03T21:31:54.5559544Z Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command
2019-10-03T21:31:54.5559595Z Version : 2.158.0
2019-10-03T21:31:54.5559626Z Author : Microsoft Corporation
2019-10-03T21:31:54.5559679Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
2019-10-03T21:31:54.5559712Z ==============================================================================
2019-10-03T21:31:55.3428758Z [command]C:\windows\system32\chcp.com 65001
2019-10-03T21:31:55.3566253Z Active code page: 65001
2019-10-03T21:31:55.5334629Z [command]C:\hostedtoolcache\windows\dotnet\dotnet.exe build d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool.csproj --no-restore
2019-10-03T21:31:55.5534100Z ##[error]Error: There was an error when attempting to execute the process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe'. This may indicate the process failed to start. Error: spawn C:\hostedtoolcache\windows\dotnet\dotnet.exe ENOENT
2019-10-03T21:31:55.5546833Z ##[error]Dotnet command failed with non-zero exit code on the following projects : d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool.csproj
2019-10-03T21:31:55.5625878Z ##[section]Finishing: dotnet build
I have now added a dotnet SDK activity to load 2.2.x version and then then an explicit dotnet restore step (even though its not needed technically as build should do a restore too). But, the restore step passes, but it fails every time in the build step.
Some partial logs from the restore process are shown below -
2019-10-03T21:30:25.5826687Z ##[section]Starting: dotnet restore
2019-10-03T21:30:25.5942577Z ==============================================================================
2019-10-03T21:30:25.5942669Z Task : .NET Core
2019-10-03T21:30:25.5942702Z Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command
2019-10-03T21:30:25.5942756Z Version : 2.158.0
2019-10-03T21:30:25.5942787Z Author : Microsoft Corporation
2019-10-03T21:30:25.5942837Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
2019-10-03T21:30:25.5942869Z ==============================================================================
2019-10-03T21:30:27.1500592Z [command]C:\windows\system32\chcp.com 65001
2019-10-03T21:30:27.7292436Z Active code page: 65001
2019-10-03T21:30:27.7296084Z SYSTEMVSSCONNECTION exists true
2019-10-03T21:30:28.0692275Z SYSTEMVSSCONNECTION exists true
2019-10-03T21:30:28.5211540Z SYSTEMVSSCONNECTION exists true
2019-10-03T21:30:28.5240738Z Saving NuGet.config to a temporary config file.
2019-10-03T21:30:28.5284543Z Saving NuGet.config to a temporary config file.
2019-10-03T21:30:28.5338058Z [command]C:\hostedtoolcache\windows\dotnet\dotnet.exe restore d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool.csproj --configfile d:\a\_temp\Nuget\tempNuGet_05ce1f4cc83beb812b37be120d7010969ab1a363.config --verbosity Detailed
2019-10-03T21:30:31.1552382Z
2019-10-03T21:30:31.1633338Z Welcome to .NET Core!
2019-10-03T21:30:31.1633445Z ---------------------
2019-10-03T21:30:31.1633487Z Learn more about .NET Core: https://aka.ms/dotnet-docs
2019-10-03T21:30:31.1633556Z Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs
2019-10-03T21:30:31.1633582Z
2019-10-03T21:30:31.1633618Z Telemetry
2019-10-03T21:30:31.1633654Z ---------
2019-10-03T21:30:31.1633712Z The .NET Core tools collect usage data in order to help us improve your experience. The data is anonymous and doesn't include command-line arguments. The data is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.
2019-10-03T21:30:31.1633881Z
2019-10-03T21:30:31.1633924Z Read more about .NET Core CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry
2019-10-03T21:30:31.1684350Z
2019-10-03T21:30:31.1686360Z Configuring...
2019-10-03T21:30:31.1686911Z --------------
2019-10-03T21:30:31.1687446Z A command is running to populate your local package cache to improve restore speed and enable offline access. This command takes up to one minute to complete and only runs once.
2019-10-03T21:30:44.4629886Z Decompressing .......... 13256 ms
2019-10-03T21:31:36.6357349Z Expanding .......... 51984 ms
2019-10-03T21:31:38.0761886Z
2019-10-03T21:31:38.0762691Z ASP.NET Core
2019-10-03T21:31:38.0762874Z ------------
2019-10-03T21:31:38.0763054Z Successfully installed the ASP.NET Core HTTPS Development Certificate.
2019-10-03T21:31:38.0763284Z To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). For establishing trust on other platforms refer to the platform specific documentation.
2019-10-03T21:31:38.0763446Z For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.
2019-10-03T21:31:38.4176357Z Build started 10/3/2019 9:31:38 PM.
2019-10-03T21:31:38.9605866Z 0>Resolving SDK 'Microsoft.NET.Sdk'...
2019-10-03T21:31:38.9816247Z Property reassignment: $(MSBuildProjectExtensionsPath)="d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\obj\" (previous value: "obj\") at C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Current\Microsoft.Common.props (56,5)
2019-10-03T21:31:38.9833374Z Property reassignment: $(MSBuildAllProjects)=";C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props;C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.props" (previous value: ";C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props") at C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.props (15,5)
2019-10-03T21:31:38.9949011Z Property reassignment: $(MSBuildAllProjects)=";C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props;C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.props;C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.props" (previous value: ";C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props;C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.props") at C:\hostedtoolcache\windows\dotnet\sdk\2.2.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.props (21,5)
...
...
...
2019-10-03T21:31:47.9997847Z Generating MSBuild file d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\GDPR.OutputProvider\obj\GDPR.OutputProvider.csproj.nuget.g.props.
2019-10-03T21:31:47.9998017Z Generating MSBuild file d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\GDPR.OutputProvider\obj\GDPR.OutputProvider.csproj.nuget.g.targets.
2019-10-03T21:31:48.0229473Z Writing assets file to disk. Path: d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\GDPR.OutputProvider\obj\project.assets.json
2019-10-03T21:31:48.0229714Z Checking compatibility of packages on .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0229774Z Checking compatibility for GDPR.Output.IO 1.0.0 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0229817Z Checking compatibility for NETStandard.Library 2.0.3 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0229859Z Checking compatibility for GDPR.Common 1.0.0 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0229916Z Checking compatibility for GDPR.Logger 1.0.0 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0229955Z Checking compatibility for GDPR.ObjectModel 1.0.0 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0229996Z Checking compatibility for WindowsAzure.Storage 9.3.3 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230054Z Checking compatibility for Microsoft.NETCore.Platforms 1.1.0 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230299Z Checking compatibility for Microsoft.Azure.KeyVault 3.0.3 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230341Z Checking compatibility for Microsoft.Azure.Management.KeyVault 2.4.3 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230394Z Checking compatibility for Microsoft.Azure.Services.AppAuthentication 1.0.3 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230457Z Checking compatibility for Microsoft.IdentityModel.Clients.ActiveDirectory 5.0.5 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230500Z Checking compatibility for Microsoft.Rest.ClientRuntime.Azure.Authentication 2.4.0 with .NETStandard,Version=v2.0.
2019-10-03T21:31:48.0230543Z Checking compatibility for System.Security.Cryptography.X509Certificates 4.3.2 with .NETStandard,Version=v2.0.
...
...
...
2019-10-03T21:31:54.4289388Z All packages and projects are compatible with .NETCoreApp,Version=v2.1.
2019-10-03T21:31:54.4454996Z Committing restore...
2019-10-03T21:31:54.4459080Z Generating MSBuild file d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\obj\MyTool.csproj.nuget.g.props.
2019-10-03T21:31:54.4460039Z Generating MSBuild file d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\obj\MyTool.csproj.nuget.g.targets.
2019-10-03T21:31:54.4461496Z Writing assets file to disk. Path: d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\obj\project.assets.json
2019-10-03T21:31:54.4567260Z Writing cache file to disk. Path: d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\obj\MyTool.csproj.nuget.cache
2019-10-03T21:31:54.4573630Z Restore completed in 4.12 sec for d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool.csproj.
2019-10-03T21:31:54.4661557Z
2019-10-03T21:31:54.4662703Z NuGet Config files used:
2019-10-03T21:31:54.4663349Z d:\a\_temp\Nuget\tempNuGet_05ce1f4cc83beb812b37be120d7010969ab1a363.config
2019-10-03T21:31:54.4664039Z
2019-10-03T21:31:54.4664744Z Feeds used:
2019-10-03T21:31:54.4665067Z https://api.nuget.org/v3/index.json
2019-10-03T21:31:54.4785886Z
2019-10-03T21:31:54.4786633Z Installed:
2019-10-03T21:31:54.4796944Z 7 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.Logger\MyTool.Logger.csproj
2019-10-03T21:31:54.4803020Z 32 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.Common\MyTool.Common.csproj
2019-10-03T21:31:54.4803472Z 33 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.OutputProvider\MyTool.OutputProvider.csproj
2019-10-03T21:31:54.4803792Z 34 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.Output.IO\MyTool.Output.IO.csproj
2019-10-03T21:31:54.4804056Z 33 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.SearchFilter\MyTool.SearchFilter.csproj
2019-10-03T21:31:54.4804362Z 32 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.PiiData\MyTool.PiiData.csproj
2019-10-03T21:31:54.4805159Z 42 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool\MyTool.SearchHandler\MyTool.SearchHandler.csproj
2019-10-03T21:31:54.4805573Z 42 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool.App\MyTool.App.csproj
2019-10-03T21:31:54.4805849Z 46 package(s) to d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool.csproj
2019-10-03T21:31:54.4806121Z Done executing task "RestoreTask".
2019-10-03T21:31:54.4806389Z 1>Done building target "Restore" in project "MyTool.csproj".
2019-10-03T21:31:54.4806658Z 1>Done Building Project "d:\a\r1\a\MyTool\DataFactory\CustomActivities\MyTool\MyTool.csproj" (Restore target(s)).
2019-10-03T21:31:54.5031887Z
2019-10-03T21:31:54.5032209Z Build succeeded.
2019-10-03T21:31:54.5032251Z 0 Warning(s)
2019-10-03T21:31:54.5032319Z 0 Error(s)
2019-10-03T21:31:54.5032343Z
2019-10-03T21:31:54.5032377Z Time Elapsed 00:00:16.08
2019-10-03T21:31:54.5417968Z ##[section]Finishing: dotnet restore
Any clues what could be going wrong?
This was happening because I had something in the 'Working Directory'. I just cleared the "Working directory" field. Before I had set it to the subfolder containing the .csproj file which was incorrect. The working directory should be the root.

Could not determine the dependencies of task ':app:preDebugBuild'

I am build an app with firebase dependencies before creating an app i have done the firebase configuration and added firebase dependencies in pubspec.yaml. But when i run the app i got some errors.
FAILURE: Build failed with an exception.
* What went wrong:
Could not determine the dependencies of task ':app:preDebugBuild'.
> In project 'app' a resolved Google Play services library dependency depends on another at an exact version (e.g. "[15.0.
1]", but isn't being resolved to that version. Behavior exhibited by the library will be unknown.
Dependency failing: com.google.android.gms:play-services-flags:15.0.1 -> com.google.android.gms:play-services-basement#[
15.0.1], but play-services-basement version was 16.0.1.
The following dependencies are project dependencies that are direct or have transitive dependencies that lead to the art
ifact with the issue.
-- Project 'app' depends on project 'firebase_auth' which depends onto com.google.firebase:firebase-auth#16.0.2
-- Project 'app' depends on project 'firebase_core' which depends onto com.google.firebase:firebase-core#16.0.4
-- Project 'app' depends on project 'firebase_database' which depends onto com.google.firebase:firebase-database#15.+
For extended debugging info execute Gradle from the command line with ./gradlew --info :app:assembleDebug to see the dep
endency paths to the artifact. This error message came from the google-services Gradle plugin, report issues at https://
github.com/google/play-services-plugins and disable by adding "googleServices { disableVersionCheck = false }" to your b
uild.gradle file.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 2s
Finished with error: Gradle task assembleDebug failed with exit code 1
The Problem occur when the dependencies cannot download from jcenter server. change your network connection follows flutter clean and try again
you can still work in debug mode
flutter run --debug will work
or you can goto File > Settings>Build,Execution,Deployment>Build Tools>Gradle>Uncheck Offline work option in Android Studio
You can also invalidate Cache and Restart

Installing SystemML from MVN/GitHub?

SystemML is available on https://github.com/SparkTC/systemml
How do I get it started with? I am newbie to GitHub.
I created a directory in my Ubuntu and copied the POM.xml file - when I issued mvn clean package, I am getting the error:
mvn clean package
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.ibm.systemml:systemml-parent:5.2-SNAPSHOT (/home/vmuser/system-ml/pom.xml) has 1 error
[ERROR] Child module /home/vmuser/system-ml/system-ml of /home/vmuser/system-ml/pom.xml does not exist
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
When I went to R and issued the following command on R 64 bit ver 3.1.1, I got error too:
> install.packages(c("batch", "bitops", "boot", "caTools", "data.table", "doMC", "doSNOW", "ggplot2", "glmnet", "lda", "Matrix", "matrixStats", "moments", "plotrix", "psych", "reshape", "topicmodels", "wordcloud", "methods"), dependencies=TRUE)
--- Please select a CRAN mirror for use in this session ---
Warning: unable to access index for repository https://cran.rstudio.com/bin/windows/contrib/3.1
Warning: package ‘methods’ is in use and will not be installed
Warning message:
packages ‘batch’, ‘bitops’, ‘boot’, ‘caTools’, ‘data.table’, ‘doMC’, ‘doSNOW’, ‘ggplot2’, ‘glmnet’, ‘lda’, ‘Matrix’, ‘matrixStats’, ‘moments’, ‘plotrix’, ‘psych’, ‘reshape’, ‘topicmodels’, ‘wordcloud’ are not available (for R version 3.1.1)
>
The error message you received tells you what the problem is (formatting mine):
The project com.ibm.systemml:systemml-parent:5.2-SNAPSHOT (/home/vmuser/system-ml/pom.xml) has 1 error
Child module /home/vmuser/system-ml/system-ml of /home/vmuser/system-ml/pom.xml does not exist
You said:
I created a directory in my Ubuntu and copied the POM.xml file
You don't just need the pom.xml file; you need the whole project. Either git clone it or download the source as a zip and extract it, then run mvn clean package from the project directory.
git clone is a better option if you intend to modify the source code. It will give you some powerful tools for integrating upstream changes and for submitting your modifications to the parent project. If you just want to use the project as-is, either option should be fine.
SystemML became an Apache (incubating) project in November of 2015. Its main website is located at http://systemml.apache.org/. The project can now be found on GitHub at https://github.com/apache/incubator-systemml.
Probably the quickest way to get started with Apache SystemML is to download a pre-built release package from the Apache SystemML Downloads page (see the main website). Information about Apache SystemML can be found at the Apache SystemML Documentation site, which is linked to from the main site. This includes information about running SystemML in notebooks, on Spark, and on Hadoop.
If you would like to clone the SystemML repository and build it locally with Maven, instructions to do so can be found in the project README on GitHub.

Resources