Warnings about javac when building QuestDB from source - questdb

I'm trying to build QuestDB from source on a newly setup machine and I get warnings about javac:
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) # questdb ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1292 source files to /home/pi/questdb/core/target/classes
[WARNING] Unable to autodetect 'javac' path, using 'javac' from the environment.
What's a fix for this?

It looks like JAVA_HOME env var is not set. You can check by running the following in your shell:
echo $JAVA_HOME
On macOS, I have the following:
/Library/Java/JavaVirtualMachines/openjdk-11.jdk/Contents/Home
To check which runtime maven (brew install) is referencing:
mvn --version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /Users/me/maven/apache-maven-3.6.3
Java version: 11.0.9, vendor: Oracle Corporation, runtime: /usr/local/Cellar/openjdk#11/11.0.9/libexec/openjdk.jdk/Contents/Home
In ~/.zshrc (you may use ~/.bashrc) I have set JAVA_HOME with
export JAVA_HOME="/Library/Java/JavaVirtualMachines/openjdk-11.jdk/Contents/Home"
then try building again:
source ~/.zshrc
mvn clean package -DskipTests -P build-web-console,build-binaries

Related

NextJS deployment on AWS amplify issue (frontend + incompatible module)

I deploy the nextjs project by connecting the github repo, the provision passes, the backend is built, but the frontend fails to build. Here is the log with the error:
# Starting phase: preBuild
# Executing command: yarn install
2021-12-13T06:55:51.568Z [INFO]: yarn install v1.22.0
2021-12-13T06:55:51.620Z [INFO]: [1/4] Resolving packages...
2021-12-13T06:55:51.815Z [INFO]: [2/4] Fetching packages...
2021-12-13T06:56:02.529Z [WARNING]: error next#12.0.7: The engine "node" is incompatible with this module. Expected version ">=12.22.0". Got "12.21.0"
2021-12-13T06:56:02.537Z [WARNING]: error Found incompatible module.
2021-12-13T06:56:02.538Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
2021-12-13T06:56:02.550Z [ERROR]: !!! Build failed
2021-12-13T06:56:02.552Z [ERROR]: !!! Non-Zero Exit Code detected
2021-12-13T06:56:02.552Z [INFO]: # Starting environment caching...
2021-12-13T06:56:02.552Z [INFO]: # Environment caching completed
Terminating logging...
The build settings:
version: 1
frontend:
phases:
preBuild:
commands:
- yarn install
build:
commands:
- yarn run build
artifacts:
baseDirectory: .next
files:
- '**/*'
cache:
paths:
- node_modules/**/*
I really do not know how to fix this, is it an AWS issue or my project has outdated packages? Any help would be appreciated 😄.
To fix this issue you have to tell Amplify which version of NodeJS to use.
Go To:
Build Settings
At the bottom is Edit Build image settings
Click Add Package Overide
Set your NodeJS version
This worked for me.

Deploy PHP application from Azure DevOps to AWS using CI/CD pipeline

I'm able to deploy the ASP.net applications from Azure DevOps to AWS environments using CI/CD pipeline YAML file. I modified the ASP.net YAML file a bit and tried to deploy the PHP application. But it didn't worked out.
Below is the modified YAML that I'm using to deploy PHP application.
Can some one help to figure out the issue in this? Am I missing any steps/ settings?
# PHP
# Test and package your PHP project.
# Add steps that run tests, save build artifacts, deploy, and more:
# https://learn.microsoft.com/azure/devops/pipelines/languages/php
trigger:
- master
pool:
vmImage: ubuntu-latest
variables:
phpVersion: 7.2
steps:
- script: |
sudo update-alternatives --set php /usr/bin/php$(phpVersion)
sudo update-alternatives --set phar /usr/bin/phar$(phpVersion)
sudo update-alternatives --set phpdbg /usr/bin/phpdbg$(phpVersion)
sudo update-alternatives --set php-cgi /usr/bin/php-cgi$(phpVersion)
sudo update-alternatives --set phar.phar /usr/bin/phar.phar$(phpVersion)
php -version
displayName: 'Use PHP version $(phpVersion)'
- script: composer install --no-interaction --prefer-dist
displayName: 'composer install'
- task: PublishBuildArtifacts#1
inputs:
PathtoPublish: '$(Build.ArtifactStagingDirectory)'
ArtifactName: 'drop'
publishLocation: 'Container'
- task: BeanstalkDeployApplication#1
inputs:
awsCredentials: 'AWS_Creds'
regionName: 'us-north-1'
applicationName: 'app_name'
environmentName: 'env_name'
description: 'New Build from Azure DevOps'
applicationType: 'version'
webDeploymentArchive: '$(build.artifactStagingDirectory)/WebApp.zip'
I'm getting the below error when I run the above pipeline script.
Starting: composer install
==============================================================================
Task : Command line
Description : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version : 2.182.0
Author : Microsoft Corporation
Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
Script contents:
composer install --no-interaction --prefer-dist
========================== Starting Command Output ===========================
/usr/bin/bash --noprofile --norc /home/vsts/work/_temp/f5188f9d-a102-4093-ad5d-0acaaa110763.sh
Composer could not find a composer.json file in /home/vsts/work/1/s
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
##[error]Bash exited with code '1'.
Finishing: composer install
Composer could not find a composer.json file in /home/vsts/work/1/s
The /home/vsts/work/1/s is the working directory where your repository will be checked out. If your composer.json file is under the root directory of repository, that is, its path is repsotiory_name/composer.json, the Command Line task will successfully run this command composer install --no-interaction --prefer-dist.
If the composer.json file is under the sub directory of repository, you need to switch current directory to its file path. For example, its path is repsotiory_name/subfolder/composer.json, below script should work as expected.
- script: |
cd subfolder
composer install --no-interaction --prefer-dist
displayName: 'composer install'

Error: VNDK library: libandroid_net's ABI has EXTENDING CHANGES

I am setting up an environment to run AOSP code on Ubuntu 18.04.1 LTS and got the error "error: VNDK library: libandroid_net's ABI has EXTENDING CHANGES". Please help me to resolve this. I have searched for hours but didn't get the solution.
I have done following things:
Installed required packages: sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev libxml2-utils xsltproc unzip
Installed community-maintained default set of udev rules for all Android devices: apt-get install adb
Install repo: https://source.android.com/setup/build/downloading.html
mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Initializing a Repo client
mkdir WORK
cd WORK
git config --global user.name "Your Name"
git config --global user.email "you#example.com"
repo init -u https://android.googlesource.com/platform/manifest
Installed pixel 3 XL binaries which include google-devices and qcom blueline. Used Extractor and ./*.sh command to extract them.
Copied qcom extracted vendor folder into Source Code and then copied pixel 3 xl vendor folder. Meged and replaced in all dialogs.
Run make clobber to clean the build directory.
Run . build/envsetup.sh to initialize the environment.
Run lunch aosp_arm-eng to select your run target as asop_arm BUILD with eng BUILDTYPE.
Run make -j16 to build the code.
Got build error:
error: VNDK library: libandroid_net's ABI has EXTENDING CHANGES
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000e7400000, 83886080, 0) failed; error='Not enough space' (errno=12)
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000cac00000, 73400320, 0) failed; error='Not enough space' (errno=12)
For 'Not enough space' error: I am setting cache and configuring jack
export USE_CCACHE=1 to enable compiler cache
Failed to do prebuilts/misc/linux-x86/ccache/ccache -M 15G because there is no ccache folder exists.
export ANDROID_JACK_VM_ARGS="-Xmx4g -Dfile.encoding=UTF-8 -XX:+TieredCompilation" to configure Jack.
For resolving the VNDK issue I am not sure by may be binaries I have included are not correct so I have deleted the vendor folder that contains Pixel 3 XL binaries.
I am a newbie for this task and just started a week ago to look into this.
Please suggest.
Thank you in advance.

What is the default location for included files when building a docker image?

derrend#laptop ~/topdir $ docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64
derrend#laptop ~/topdir $ pwd; ls *
$HOME/topdir
Dockerfile
afolder:
afile
As I understand it, when I execute a docker build the afolder and its contents will be included inside my docker image but where will they be placed if I do not designate a location in the Dockerfile?
Those files are not part of the built (end-result) image.
They are part of the build context passed to the daemon during the build process, to be used by Dockerfile directives like ADD or COPY or RUN.
A build’s context is the files located in the specified PATH or URL
For example, run this command to use a directory called docker in the branch container:
$ docker build https://github.com/docker/rootfs.git#container:docker
This is managed by Context and ModifiableContext.

Build error from Installing Apache Zeppelin

I am at my wits end trying to get Apache Zeppelin running on my linux VM. I am following this tutorial:
http://madhukaudantha.blogspot.ca/2015/03/building-apache-zeppelin.html
I have done the following:
git clone to the machine
now trying to run 'mvn clean package'
I get the following error summary, I really need to get this running.
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin .......................................... SUCCESS [16.124s]
[INFO] Zeppelin: Interpreter ............................. SUCCESS [36.026s]
[INFO] Zeppelin: Zengine ................................. SUCCESS [27.440s]
[INFO] Zeppelin: Spark ................................... SUCCESS [53.438s]
[INFO] Zeppelin: Markdown interpreter .................... SUCCESS [6.041s]
[INFO] Zeppelin: Angular interpreter ..................... SUCCESS [7.397s]
[INFO] Zeppelin: Shell interpreter ....................... SUCCESS [4.140s]
[INFO] Zeppelin: Hive interpreter ........................ SUCCESS [1:09.114s]
[INFO] Zeppelin: Tajo interpreter ........................ SUCCESS [15.153s]
[INFO] Zeppelin: web Application ......................... FAILURE [0.492s]
[INFO] Zeppelin: Server .................................. SKIPPED
[INFO] Zeppelin: Packaging distribution .................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:57.426s
[INFO] Finished at: Wed Apr 29 12:18:39 EDT 2015
[INFO] Final Memory: 78M/266M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.23:install-node -and-npm (install node and npm) on project zeppelin-web: The plugin com.github.eirslett:fron tend-maven-plugin:0.0.23 requires Maven version 3.1.0 -> [Help 1]
[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 follow ing articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginIncompatibleExceptio n
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :zeppelin-web
I have tried contacting the apache incubator team through their email (users#zeppelin.incubator.apache.org) however the emails bounced back. Ill continue to bounce around looking for a solution.
Download , extract and install Maven3 (if not already installed) and set maven in PATH
export PATH=$PATH:$MAVEN_HOME/bin
even i have updated the PATH variable with latest maven. mvn -version shows 2.x
now manually updated the maven using update-alternatives.
bdalab#solai:/opt$ sudo update-alternatives --install /usr/bin/mvn mvn $MAVEN_HOME/bin/mvn 1
bdalab#solai:/opt$ sudo update-alternatives --config mvn
Now, select a number referring to the recent maven3 installation, from the list of choices
I tried mvn install -DskipTests, with the following system configurations:
1) Java 7
2) Maven 3.3 - Download tar file. extract and update MAVEN_HOME in /etc/profile. Then run 'source' command
3) Spark 0.9.0
4) CDH4 cluster
Build is successful for me.
you can test your node and npm download url with wget first:
wget XXXnode-12.4.tar.gz
if this url can't download the file may be your network issuel
I think that you might be missing the installation of nodejs, npm. Please install nodejs, npm.
sudo yum install nodejs npm --enablerepo=epel
In my case below git config worked :
git config --global url."https://".insteadOf git://
Make sure Maven > v3.0 , npm , nodejs and bower should be installed.
For the issue was that I was using maven 3.2.
Installed maven 3.3.3 and everything went fine, build again and everything went ok.
I've the same problem with zeppelin and found the root cause to be a failure with 'bower install' command.
First you need to install nodejs
yum install -y node
then install bower
npm install -g bower
then install grunt
npm install -g grunt
run the following commands with a non-root user (i.e., create a zeppelin user)
cd zeppelin-web
bower install (takes some time to complete)
cd ..
mvn clean package -rf :zeppelin-web
https://github.com/NFLabs/zeppelin/issues/320
Switching github from git:// to https:// will do the trick.