I am trying to Merge my local branch to Target branch on server VSTS but it always failed by saying below error message:-
EXEC:EXEC(0,0): Error : not found: python2
My local publish works well but only issue when merging any source to target branch on VSTS.
I am able to resolve this issue by adding following command :-
Only issue was that Python was not installed on server, so these 2 command will help you to install that package:-
1) npm install nan
2) npm install node-sass
it works like a charm, thanks everyone for your reply.
Related
Started encountering this issue after pushing changes which has nothing to do with the node_modules or the deployment pipeline.
This issue is also seen when trying to rerun an already successful deployment in bitbucket.
I even tried updating the some of the packages to the latest version, but it still throws the same error.
But locally in my pc I have no issue with npm run build.
When the bitbucket pipeline is run.
The docker first installs node_modules using the npm install cmd.
After this while running npm run build the pipeline is failing with the error shown in the image above.
So I suspect it is the packages in the node_modules that are newly getting downloaded, because locally I have no problem with the build cmd.
Could anyone help me out, whether it is the incompatibility between the npm packages or the pipeline itself, Or if there might be any other error.
Thank you
Thanks to #Nitheesram Rajes I was able to fix this issue by updating typescript package using the command
npm install --save-dev typescript#latest
I am trying to package an electron application. when i try npm run publish:win64, it fails and gives checksum mismatch error.
Windows build tools are installed properlly as shown in the screenshot.
tried node-gyp install too.
repo: https://github.com/austonpramodh/ytmdesktop
I have tried the same repo in other pc and it works fine.
the solution was to use yarn instead of npm, as npm has some issues with electron-builder. Using yarn solved all the problems.
The image that I have attached is a screenshot from electron-builder Github page.
I want to try polymerize so I have found and use that post. But I met issues when try command
pub run polymerize:polymerize build
It works some time and then return bazel's error:
2017.35.08 16:35:06.015 polymerize [INFO]: Running bazel ...
____Loading package:
ERROR: while parsing ':all': error loading package '': Encountered error while reading extension file 'BUILD.test_app.bzl': no such package '#build_files//': No WORKSPACE file found in /private/var/tmp/_bazel_kelegorm/df7a1dbca8a607bc3485e726bb483b2b/external/build_files.
How can I solve that problem? Why it happens? Why I can't find any mention about that error? What have I missed?
Thanks!
There was a problem with newest bazel versions. Just upgrade to latest polymerize (v. 0.8.6+1) and it should work again.
To start from a clean workspace just do a :
git clone git#github.com:polymer-dart/todo_ddc.git
cd todo_ddc
pub get
pub run polymerize:polymerize build
I recently tried to setup Google Firebase Analytics for my Unity game. I am building it for iOS exclusively. I have not been able to get Firebase working unfortunately.
I am using Xcode 8.1, OSX 10.12.1, and Unity 5.5.0f3
Whenever I try to build to iOS from Unity, I get this error in console:
Error running cocoapods. Please ensure you have at least version 1.0.0. You can install cocoapods with the Ruby gem package manager:
sudo gem install -n /usr/local/bin cocoapods
pod setup
'pod --version' returned status: 127
output:
UnityEngine.Debug:LogError(Object)
Google.IOSResolver:Log(String, Boolean, LogLevel)
Google.IOSResolver:OnPostProcessInstallPods(BuildTarget, String)
UnityEditor.HostView:OnGUI()
I have tried just about every suggestion I could find online. I have installed Cocoapods version 1.1.1, and later I tried the beta version 1.2.0.beta.1, nothing has worked.
Typing "which pod" in my terminal yields: /usr/local/bin/pod
Typing "pod --version" in my terminal yields the correct version number (i.e.: 1.2.0.beta.1)
I cannot get this build to work in my game's project, or a completely empty project to which I just imported firebase and tried to build.
I also tried to get this working with the sample project at the following link with no success: https://github.com/firebase/quickstart-unity
I am out of ideas here... can anyone help?
Much appreciated!
Firebase engineer here.
The code reporting the error is here:
https://github.com/googlesamples/unity-jar-resolver/blob/b7a90e43d6c893622102ca53681f53a58dab1a24/source/IOSResolver/src/IOSResolver.cs#L760
unfortunately, it looks like we're not logging the stderr stream so it's tricky to see how this is failing.
It sounds like your pod tool is returning a non-zero error code, not sure why. For example, on my machine I see the following:
$ which pod
/usr/local/bin/pod
$ pod --version ; echo $?
1.1.1
0
As you can see "pod --version" is returning "0" (success).
Similarly, pulling the latest Cocoapods tool from github https://github.com/CocoaPods/CocoaPods yields:
cd CocoaPods
export RUBYLIB=$(cd lib ; pwd)
export COCOAPODS_NO_BUNDLER=1
$ ./bin/pod --version ; echo $?
1.2.0.beta.1
0
Where the same thing is happening, the pod tool is returning a success exit code.
Things to try:
Contact support#firebase.google.com - we'll be able to work directly with you to diagnose and resolve this issue.
Try changing your LANG variable, we've been tripped up by this code https://github.com/CocoaPods/CocoaPods/blob/8db5956/bin/pod#L3 in the past. It's supposed to be handled by https://github.com/googlesamples/unity-jar-resolver/blob/b7a90e4/source/IOSResolver/src/IOSResolver.cs#L743 but you never know.
If you feel brave, build https://github.com/googlesamples/unity-jar-resolver/ yourself (you should be able to run ./gradlew in the root directory to build the DLLs) then you can add the stderr reporting, post / diagnose the error you're running into.
Cheers,
Stewart
If you have this error in your output:
Failed to extract git version from `git --version` ("xcrun: error: active developer path (\"/Applications/Xcode.app/Contents/Developer\") does not exist\nUse `sudo xcode-select --switch path/to/Xcode.app` to specify the Xcode that you wish to use for command line developer tools, or use `xcode-select --install` to install the standalone command line developer tools.\nSee `man xcode-select` for more details.\n") (RuntimeError),
...and IF you have a different path to XCode (like in my case, I had Xcode beta), then you should run the command:
sudo xcode-select --switch /Applications/Xcode-beta.app/
I have a ASP.Net 4.5 MVC application which uses Angular 1.5. The JS code is Typescript and a post build action builds the js code and deploys it to the folder where my application refers to.
I have a Slot on my azure web app which is backed my gitlab repo. Committing to the repo, triggers the deployment, however the post deployment build frequently seems to have issues when a bower/npm or typings library is updated (which is resolved by manually clearing the folder via the kudu console). Does someone have an example of a deploy.cmd script which does the equivalent of
npm install
typings install
at the correct point in the pipeline so that the files get deployed correctly.
I want to start scratch with a new slot, and to get the existing slot to work in the past i had to manually install typings for example "npm install typings --global" in order to get the build to work without a typings error.
Update Output Below
I'm guessing that the errors below are due to azure running typescript 1.6 compiler over reference files which need typescript > 1.6.
My csproj has <TypeScriptToolsVersion>2.0</TypeScriptToolsVersion>
(ive removed my files from the compile output, but the _all.d.ts file does reference the errored files below
CompileTypeScript:
D:\Program Files (x86)\Microsoft SDKs\TypeScript\1.6\tsc.exe --sourcemap --target ES5 --noEmitOnError "REMOVED MY TYPESCRIPTFILES" "D:\home\site\repository\mymvcproject\app\src\_all.d.ts"
D:\home\site\repository\mymvcproject\typings\globals\angular\index.d.ts(1824,32): error TS1110: Build: Type expected. [D:\home\site\repository\mymvcproject\mymvcproject.csproj]
D:\home\site\repository\mymvcproject\typings\globals\angular\index.d.ts(1824,50): error TS1005: Build: ']' expected. [D:\home\site\repository\mymvcproject\mymvcproject.csproj]
D:\home\site\repository\mymvcproject\typings\globals\angular\index.d.ts(1824,58): error TS1005: Build: ',' expected. [D:\home\site\repository\mymvcproject\mymvcproject.csproj]
D:\home\site\repository\mymvcproject\typings\globals\angular\index.d.ts(1824,59): error TS1136: Build: Property assignment expected. [D:\home\site\repository\mymvcproject\mymvcproject.csproj]
D:\home\site\repository\mymvcproject\typings\globals\angular\index.d.ts(1941,1): error TS1128: Build: Declaration or statement expected. [D:\home\site\repository\mymvcproject\mymvcproject.csproj]
Done Building Project "D:\home\site\repository\mymvcproject\mymvcproject.csproj" (Build;pipelinePreDeployCopyAllFilesToOneFolder target(s)) -- FAILED.
FINAL UPDATE
After the typescript team finally generated a version of typescript 2.* which could be installed on Azure, and then the Kudu team deployed it. Now the whole process works! the note from below about using
"preinstall": "npm install typescript -g && npm install typings -g"
Was the other part of the solution!
According to your requirement, you could follow the steps below to achieve your purpose.
Create a deployment script
You could log in to KUDU tool (https://.scm.azurewebsites.net/), click "Tool" > "Download deployment script". Also, you could leverage azure-cli to generate the script. For more details about how to generate deployment script via azure-cli, you could refer to this tutorial.
Customize the deployment script
For using NPM to manage your packages, you could add the following scripts in your package.json file.
"scripts":{
"preinstall": "npm install typescript -g && npm install typings -g"
}
Then, you need to add the following scripts to the deploy.cmd file.
IF EXIST "%DEPLOYMENT_SOURCE%\package.json" (
pushd "%DEPLOYMENT_SOURCE%"
echo installing npm package
call :ExecuteCmd npm install --production
IF !ERRORLEVEL! NEQ 0 goto error
popd
)
Or you could add the following scripts to install typescript and typings directly via command line.
echo Installing typescript and typings
call npm install typescript -g && npm install typings -g
IF !ERRORLEVEL! NEQ 0 goto error
Note: The .deployment, deploy.cmd files need to be placed in the root directory of your solution. You could refer to this sample project for details.