Appc is successfully setup via terminal. Each prerequisite installed but on Studio launch Appcelerator cannot find/recognize installed node and tries to install node again and prompts "cannot install node on platforms other than windows or mac".
Since I am using the latest version of Titanium so it requires the latest Node.js (nodejs, node and npm). Appcelerator tries to install node because it does not find any compatible version.
Secondly Appcelerator tries to install all pending prerequisites and it cannot install node on platforms other than windows or mac so you have to install nodejs via terminal.
To debug issues try to run programs via terminal. Particular to Appcelerator in Ubuntu, go the directory and run it by command $ ./AppceleratorStudio
It will prompt all ERRORS, WARNINGS and NOTICES.
Related
On win 10, After installing RoR 3.x and Ruby 7.x, and sqlite 3.x, the server will not start from CLI, I am not using Windows Powershell but the CMD window.
Does any part of the install of those packages require Admin window?
Does the "bin/rails server" command require Admin privileges from CLI.
Thank You
Not really.
I installed Rails in my Windows Computer, but I needed to install Node and Yarn as well.
I suggest you install WSL for Windows. It's like have Linux install but using Windows. It's faster than Windows and you will have less problems by installing Rails or any other software.
Check this link: https://learn.microsoft.com/es-es/windows/wsl/install
You need to use PowerShell as Administrator and run the command wsl --install (see pc requirements)
I'm trying to install Chromium with Chocolatey: choco install -y chromium
I get the following output:
Installing the following packages:
chromium
By installing, you accept licenses for the packages.
Progress: Downloading chromium 104.0.5112.102... 100%
chromium v104.0.5112.102 [Approved]
chromium package files install completed. Performing other installation steps.
Chromium 104.0.5112.102 is already installed.
Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type `refreshenv`).
The install of chromium was successful.
Software installed to 'C:\Program Files\Chromium\Application'
Chocolatey installed 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
However, no folder is created for the Chromium application in C:\Program Files. I am getting a new installation of the NuGet for Chromium in C:\ProgramData\chocolatey\lib\chromium.
I'm doing this as part of an attempt to automate a Chromium installation, so I've been messing around with lots of different chromium versions and force installs. The line Chromium 104.0.5112.102 is already installed. looks pretty suspect, as does the note in the Chocolatey chromium page that says that sometimes the package will be installed on %localappdata%\Chromium instead, but I can't find chromium installed in C:\Users\jkatofsky\AppData\Local either.
I feel like the issue is just within reach, but I can't figure it out. Any ideas?
The package is already installed (note I said package) so it won't be installed again. I think messing around with versions has caused that issue.
Uninstall the package and install it again.
Doing choco uninstall -n --skipautouninstaller chromium and going to Control Panel -> Programs -> Uninstall a program then uninstalling Chromium, and getting rid of it from the registry when prompted, fixed things for me. The next choco install chromium worked as expected.
I am using windows and didn't wanted to switch to linux. I still wanted to learn it so I downloaded ubuntu subsystem for windows. It works fine and I can also execute linux commands on it. But the problem is I can't check my pip version using "pip --version" command also I can't access nodejs . It says that node isn't recognized. But it is working fine on my cmd windows terminal. How can I make it work ? Do I really have to download all these packages again after running "sudo apt update" command.
Yes, you have to download all these packages again for Ubuntu-WSL. That is because WSL is not compatible with windows executable, just like Ubuntu is supposed to be.
I've been following the tutorial at https://learn.microsoft.com/en-us/azure/iot-edge/tutorial-python-module
On my development machine, the python lint in Visual Studio Code is reporting the error: E0401:Unable to import 'iothub_client' on main.py.
I wonder if I'm missing a pre-requisite step, or is this just an advisory that can be ignored on the development side of things and it should be ok once deployed - or do I need to fix this error on the development machine first?
I've successfully run the previous tutorial and have tempSensor running. filterSensor seems to terminate and go into a "backoff" state once deployed, with an error of 1. I don't know how I can find out on the Edge-side why it is failing - how do I go about debugging this? Can I see print statement output anywhere, for example?
I'm developing on Mac, and deploying to a Beaglebone running Ubuntu 16.04 LTS.
For the Python lint issue, yes you are right that this information is just advisory. The cause for it showing up is that you did not install Azure IoT Python SDK which is a pip package on your development machine. You can safely ignore it because the SDK will be installed when building the module image (there is a RUN pip install -r requirements.txt step in the Dockerfile).
If you want to resolve this lint information, you can install the SDK on your development machine manually by running pip install -r requirements.txt in the root folder of the module.
Platform: Ubuntu 14.10
Appium - 1.3.7
One similar question I had come across -
How to setup Appium in Ubuntu for android
and following suggestion, I install npm via HomeBrew
And eventually, appium execution fails with error -
error: Appium will not work if used or installed with sudo. Please rerun/install as a non-root user. If you had to install Appium using `sudo npm install -g appium`, the solution is to reinstall Node using a method (Homebrew, for example) that doesn't require sudo to install global npm packages.
Is there anything I missed?
Appium allows to run under sudo since 1.2.3: source
apparently I was on wrong directory when invoking invoking appium. I should be in /node-v0.12.2-linux-x64/bin$ and invoke appium.
even though I was in wrong directory, the error message I received was so descriptive (and misleading) that it made me believe that I installed appium in wrong way.