Gradle error when copy to Dist Folder - gradle

Can somebody help me with this
Image here
Sorry because I am not having enough reputation. =)

This error say :
Path too long
When you extract compressed files from the installation media, you might see a Error 0x80010135: File path too long error.
The error is caused when you use Windows Explorer or WinZip to extract files and it encounters a file path that exceeds the maximum character limit.
To resolve this problem, use a decompression utility such as 7-Zip, that can handle long file paths. Otherwise, extract the files to the root directory or to the c:/temp directory.

Related

Error while compiling the substrate-node-template on windows vscode

error: failed to write bytecode to F:\substrate-node-template\substrate-node-template-master\target\release\wbuild\node-template-runtime\target\wasm32-unknown-unknown\release\deps\pallet_transaction_payment_rpc_runtime_api-927dd9f7f5859937.pallet_transaction_payment_rpc_runtime_api.a5dcb31e-cgu.0.rcgu.bc: The system cannot find the path specified. (os error 3)
enter image description here
Note that Windows systems have a restriction on path length, and sometimes substrate runs into this! Better to put your build folder closer to your root dir to minimize path length. More in this issue(https://github.com/substrate-developer-hub/substrate-node-template/issues/185)
it's a dup question, though.

The specified path, file name, or both are too long when deploying WebJob to Azure

I've recently upgraded a project to .NET Framework 4.6.1 and now am having issues when trying to deploy to Azure as a WebJob. I'm getting the following error:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Web\Microsoft.Web.Publishing.targets(2603,5):
Error : Copying file
C:\Users\XXXXXXXXXXX\Documents\Source\Workspaces\XXXXX Server
Application\ServerApplication\XXXXXXXX.IntegrationService\bin\Release\Microsoft.Extensions.DependencyInjection.Abstractions.dll
to
obj\Release\Package\PackageTmp\app_data\jobs\continuous\XXXXXXXXIntegrationService\Microsoft.Extensions.DependencyInjection.Abstractions.dll
failed. The specified path, file name, or both are too long. The fully
qualified file name must be less than 260 characters, and the
directory name must be less than 248 characters.
I'm confused by the error as the path and filename are only 189 characters combined:
C:\Users\XXXXXXXXXXX\Documents\Source\Workspaces\XXXXX Server Application\ServerApplication\XXXXXXXX.IntegrationService\bin\Release\Microsoft.Extensions.DependencyInjection.Abstractions.dll
If I remove the Microsoft.Extensions.DependencyInjection.Abstractions.dll from my project I can then deploy as normal. I've tried cleaning the solution and restarting VS.
I'm confused by the error as the path and filename are only 189 characters combined
That because event if the error as the path and filename are only 189 characters combined in below path:
C:\Users\XXXXXXXXXXX...bin\Release\Microsoft.Extensions.DependencyInjection.Abstractions.dll
But when we publishing the project, VS/MSBuild will copy this file to the path:
obj\Release\Package\PackageTmp\app_data\jobs\continuous\XXXXXXXXIntegrationService\Microsoft.Extensions.DependencyInjection.Abstractions.dll
So the full path and filename should be:
C:\Users\XXXXXXXXXXX\Documents\Source\Workspaces\XXXXX Server
Application\ServerApplication\XXXXXXXX.IntegrationServiceobj\Release\Package\PackageTmp\app_data\jobs\continuous\XXXXXXXXIntegrationService\Microsoft.Extensions.DependencyInjection.Abstractions.dll
Then the path and file name are about 260 characters combined, so VS/MSBuild could not access that path. To resolve this issue, you can try to move your solutions/projects to the the root directory, like:C:\Workspaces

Creating Setup of large data with NSIS Script

I am creating setup of large data approximetly 10 GB with NSIS Script and trying to create a single setup (exe). Its giving an Error -
Internal compiler error #12345: error mmapping file (xxxxxxxxxx, xxxxxxxx) is out of range.
Note: you may have one or two (large) stale temporary file(s) left in your temporary directory (Generally this only happens on Windows 9x).
Please tell me how to solve this issue ?
Is there any other way to create a setup for this kinda situation ?
NSIS installers are limited to 2Gb.
If you absolutely need it to be one file and you want to continue to use NSIS you have to append the data to the end of the generated setup. I'm not sure I would recommend that approach but it could work if the appended data is a zip file (or some other format with the header at the end) and you use one of the NSIS zip plugins to extract at run-time...
I have used https://sourceforge.net/projects/nsisbi/ instead of normal NSIS. It solved the problem.
I was using Silent Install Builder 5 and received this same error with a package installer that had LESS that 2 GB total. Once I determined that the NSIS compiler was to blame, I began experimenting with several possible solutions and here's what worked: I downloaded the newer NSISBI compiler from here https://sourceforge.net/projects/nsisbi/ and then did these 3 steps:
Go to C:\Program Files (x86)\Silent Install Builder 5 and renamed the default NSIS folder to a new name.
Copied the NSISBI folder into the C:\Program Files (x86)\Silent Install Builder 5 directory and renamed IT to NSIS.
Tries to compile some large packages above and just below 2GB and the first few tries I would get missing file errors in the Silent Install Builder 5 compiling box. No worries because the missing files are in the old NSIS folder, that's why y9u don't delete it.
Each time find the missing file error displays, find the missing files and copy them into the same folder location in the new NSIS folder. About 3 times you will do this until there are no more errors at all and you can then include the large files without generating the "internal compiler error #12345: error mmapping file xxxx is out of range." error message. NSISBI works!

F3 caching issue

Recently, I got error
Warning: require_once(account_header.php): failed to open stream: No
such file or directory in
/home/contestium/dev/temp/dev.contestium.com.tpl.0oyr4na on line 1
Fatal error: require_once(): Failed opening required
'account_header.php' (include_path='.:/usr/share/pear:/usr/share/php')
in /home/contestium/dev/temp/dev.contestium.com.tpl.0oyr4na on line 1
I have disabled caching with
F3::set('CACHE',FALSE);
But it was not helpful for me. Any help will be appreciated. Thank you!
When using cached files, your relative path won't work, as the cached files are not in the original file's directory.
You'll either need to provide the full path to 'account_header.php', or add the path to the directory containing such to your include path. This can either be done in your php.ini file, or at [runtime][1].
It looks like the cached files are still being used, right? If you delete those files, will it fetch the original file (and not the cached files)?

VS2010 "Could not write lines to file".........."Network path not found"

does anybody know what this error in VS2010 means (i did try google but not much came up for this case on ATI stream)
Error 9 error MSB3491: Could not write lines to file "\\samples\\opencl\\bin\\debug\\x86_64\\MatrixMulDoubleVS10.exe.embed.manifest". The network path was not found. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets 673
Im trying to run the ATI Stream SDK examples
modify \MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets
<!--<WriteLinesToFile
Condition="!EXISTS('$(InputManifest)')"
File="$(InputManifest)"
Lines=""
Overwrite="false"
Encoding ="Unicode"
/>-->
<WriteLinesToFile
Condition="!EXISTS('%(Manifest.OutputManifestFile)')"
File="%(Manifest.OutputManifestFile)"
Lines=""
Overwrite="false"
Encoding ="Unicode"
/>
Leaving the drive qualifier off the output and intermediate directory paths can cause this problem.
I had a same error in my downloaded sample which was from VC6++. There were errors because output directory and intermediate directory were not given properly. I corrected them and problem was solved.

Resources