I am running aerospike 3.6.0 community eddition on ubuntu12.04 when I type aql it start prompting below WARN due to which I am not able to run any query.
~/Downloads/aerospike-server-community-3.6.0-ubuntu12.04$ aql
2015-09-08 11:57:29 WARN AEROSPIKE_ERR_TIMEOUT
2015-09-08 11:57:30 WARN AEROSPIKE_ERR_TIMEOUT
Aerospike Query
Copyright 2013-2015 Aerospike. All rights reserved.
aql> 2015-09-08 11:57:31 WARN AEROSPIKE_ERR_TIMEOUT
2015-09-08 11:57:32 WARN AEROSPIKE_ERR_TIMEOUT
2015-09-08 11:57:34 WARN AEROSPIKE_ERR_TIMEOUT
2015-09-08 11:57:35 WARN AEROSPIKE_ERR_TIMEOUT
2015-09-08 11:57:37 WARN AEROSPIKE_ERR_TIMEOUT
2015-09-08 11:57:38 WARN AEROSPIKE_ERR_TIMEOUT
How can I stop warning?
Interesting. Is your server actually running on localhost port 3000? Those are the defaults for aql. Something is running there that aql is trying and failing to connect to.
Related
explain it my screensht
i don't know how to do it as i didn't know how to do it but i tried this 'npm audit fix --force' please help me
i get this error
npm WARN deprecated source-map-url#0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated opn#6.0.0: The package has been renamed to `open`
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
changed 204 packages, and audited 205 packages in 9s
2 high severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details
DON'T PANIC! Just kidding of course...
npm has evolved during the years and protect it's users against potentials security risks. If the selected package is using old-versioned or risky dependencies, it may raise some warning regarding to the package integrity. First let's have a look on the official package page, and right up we see this:
This is a little development server with live reload capability. Use
it for hacking your HTML/JavaScript/CSS files, but not for deploying
the final site.
Now, we instantly know that the main purpose of this package is to mimic a live server for web apps, as well as we know that the author himself does not recommend using this in production
Why does this matter? Well, if we intended to use it locally, and build our production project without it, there is a very small risk of using it locally (as long as your local build is NOT deployed from your machine to a remote machine / service)
If we want to take it on the safe side, a quick search (using npm search) will result with similar yet better supported packages like livere-load. Just compare the weekly downloads stats and how much dependencies it got (the more dependencies a package use - the more risk you'll have that some of them are outdated and may result with security risks) to get an educated guess whenever the package you are using is suitable for your needs or not
Cheers
E:\React native\Demo>npm install -g expo-cli
npm WARN deprecated joi#14.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated joi#11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek#4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated topo#2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek#6.1.3: This module has moved and is now available at #hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated topo#3.0.3: This module has moved and is now available at #hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN tarball tarball data for #expo/traveling-fastlane-linux#1.10.0 (sha512-+9Mjvs9m15Meexp00A2JDXLfQHwcgua1dI0ldqVboHblzTACTMvXrfHmewxBoIBLZ45c1lLuIHD7+3UAnBHVCA==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for #expo/traveling-fastlane-darwin#1.10.0 (sha512-Ry9gHhDIPjSnP5lvtUcR7LoE5vU2Ngn893B22PYEk1RuwJG5m7ezKSGyXjs3W1WVUvPW/2+ikF1YjrNyPAIrqQ==) seems to be corrupted. Trying one more time.
[ ......] \ extract:rxjs: WARN tarball tarball data for #e**strong text**
Install #expo/traveling-fastlane-linux first with
npm i -g #expo/traveling-fastlane-linux
before installing expo-cli globally via npm.
This worked for me. Hope this helps others who are facing the same issue.
I am trying to install the expo-cli using nvm but for some reason it will get to a certain point during installation and then just stop.
I have tried using different node versions along with trying to remove the permissions that could of potentially been blocking the installation but still no luck. This is what shows in the console:
npm WARN deprecated joi#14.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/sup
port). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable
to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated #babel/polyfill#7.4.4: ? As of Babel 7.4.0, this
npm WARN deprecated package has been deprecated in favor of directly
npm WARN deprecated including core-js/stable (to polyfill ECMAScript
npm WARN deprecated features) and regenerator-runtime/runtime
npm WARN deprecated (needed to use transpiled generator functions):
npm WARN deprecated
npm WARN deprecated > import "core-js/stable";
npm WARN deprecated > import "regenerator-runtime/runtime";
npm WARN deprecated joi#11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/sup
port). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable
to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated topo#2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/sup
port). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable
to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek#4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/sup
port). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable
to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated topo#3.0.3: This module has moved and is now available at #hapi/topo. Please update your dependencie
s as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated hoek#6.1.3: This module has moved and is now available at #hapi/hoek. Please update your dependencie
s as this version is no longer maintained an may contain bugs and security issues.
npm WARN tarball tarball data for #expo/traveling-fastlane-linux#1.9.11 (sha512-xCHnqKfwWYygQfRbi9MGNSG28EHKDtzMB+QDklSH
1GeD90TA0beAjlNF+Z+KPxj28s3WZlQr9yw1AqBS7aipcw==) seems to be corrupted. Trying one more time.
Which terminal are you using ? If it's GitBash so the issue arises there try using any other terminal and it works.
I had this exact same problem ("tarball data for #expo/traveling-fastlane-linux#1.9.11 seems to be corrupted") on the command line (instead of powershell) on Windows 10, and running cmd as administrator solved the issue.
I have the same problem. It looks like is a permission issue. Following the documentation I reinstall npm with a node version manager. As I'm a linux user, I use nvm (check the documentation to chose the adequate manager for your system).
After uninstalled both npm and node, I ran:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.1/install.sh | bash
Check installation using:
command -v nvm
The output must be nvm.
Finally, run:
npm install -g expo-cli
I'm trying to create a Laravel Nova tool but when I do via the command line, after the first prompt (see below), I get this error
Would you like to install the tool's NPM dependencies? (yes/no) [yes]:
>
npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
I've run npm i -g npm but that doesn't seem to have fixed the problem. I can't seem to solve this, any ideas of how I can get this working?
In npm version 6.0.0, executing the npm install command reports this message:
up to date in 13.576s
[!] 52 vulnerabilities found [15904 packages audited]
Severity: 8 low | 40 moderate | 4 high
Run `npm audit` for more detail
Why does this appear, and how can it be disabled?
It’s a new feature, introduced with npm#6. It shows all vulnerabilities your dependencies got (excluding peerDependencies)
You can disable the warning for single package installations with the --no-audit flag.
To deactivate it for all installations you can execute npm set audit false