I am following the process from https://hardhat.org/tutorial/creating-a-new-hardhat-project to create a new hardhat project.
However, it is throwing an error in the contract compiling step; i.e. when I run yarn hardhat compile
Downloading compiler 0.8.9
(node:3732) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Error HH502: Couldn't download compiler version list. Please check your internet connection and try again.
HardhatError: HH502: Couldn't download compiler version list. Please check your internet connection and try again.
at /mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/solidity/compiler/downloader.ts:149:17
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at CompilerDownloader.downloadCompiler (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/solidity/compiler/downloader.ts:142:5)
at SimpleTaskDefinition.action (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/builtin-tasks/compile.ts:551:9)
at Environment._runTaskDefinition (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/core/runtime-environment.ts:308:14)
at Environment.run (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/core/runtime-environment.ts:156:14)
at SimpleTaskDefinition.action (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/builtin-tasks/compile.ts:678:36)
at Environment._runTaskDefinition (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/core/runtime-environment.ts:308:14)
at Environment.run (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/core/runtime-environment.ts:156:14)
at Environment._runTaskDefinition (/mnt/a/projects/Ethereum/hh-fcc/hardhat-simple-storage-2/node_modules/hardhat/src/internal/core/runtime-environment.ts:308:14)
Caused by: Error: getaddrinfo EAI_AGAIN binaries.soliditylang.org
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command
I'm running the code on windows with WSL using
node v16.13.2
yarn v1.22.15
hardhat v2.11.2
Here are my WSL configs
BUILD: 19042
BRANCH: vb_release
RELEASE: Ubuntu 20.04.3 LTS
KERNEL: Linux 4.4.0-19041-Microsoft
UPTIME: 0d 3h 18m
Here's my hardhat.config.js
require("#nomicfoundation/hardhat-toolbox");
/** #type import('hardhat/config').HardhatUserConfig */
module.exports = {
solidity: "0.8.9",
};
Here's my repo link: https://github.com/J0SAL/hardhat-simple-storage
The code and everything are correct.
I found the issue in my WSL setup.
Right now I'm using Windows PowerShell and it's working fine.
Related
After pruning with the command "docker system prune -a" nodejs wont build anymore beacuse trix.css is missing. I am assuming this was probably deleted while pruning. How can I resolve this error (see the error below)? Why is it not created again while building the container again since the file is in the docker file.
Required path doesn't exist: /code/bower_components/trix/dist/trix.css trix
[13:57:39] 'vendorcss' errored after 1.63 ms
[13:57:39] Error: Promise rejected without Error
at Domain.onError (/usr/local/lib/node_modules/gulp/node_modules/async-done/index.js:49:15)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Domain.emit (events.js:211:7)
at Domain._errorHandler (domain.js:134:21)
at process._fatalException (bootstrap_node.js:375:33)
[13:57:39] 'staging' errored after 41 ms
ERROR: Service 'nodejs' failed to build: The command '/bin/sh -c gulp staging' returned a non-
zero code: 1
Usually I use this command : "sudo docker-compose -f docker-compose-staging.yml build nodejs" when I want to build the container again. I am very new to this and would be greatfull for some help.
For me, this was the case:
The issue exists because trix.css was removed in the latest version. It has nothing to do with docker system prune as far as I understand.
You can compare the two versions here: https://github.com/basecamp/trix/compare/1.3.1...v2.0.0
Basically, in order to fix this issue, you need to do
yarn install
yarn build
inside bower_components. This is suggested in the official updated README of the trix repository: https://github.com/basecamp/trix.
Once done with that, you will have trix.css and trix.umd.min.js files for your perusal.
I have a nodejs application, and configured to run on port 5001. When I try to run the node server using node server.js, it throws me an malloc error like below
node(6080,0x1067aa600) malloc: *** error for object 0x7ffb503d2670: pointer being freed was not allocated
node(6080,0x1067aa600) malloc: *** set a breakpoint in malloc_error_break to debug
zsh: abort node server.js
My machine configs are
Processor - 2.4 GHz 8-Core Intel Core i9
Memory - 32 GB 2667 MHz DDR4
When I try to run this server, I do not run any other node server. I also checked all the processes running but nothing clashes with it. Maybe I am missing something. I tried running it on different ports as well, but i get the same error
My node js version is v14.16.1
npm version is 6.14.12
Xcode version is 13.4.0.0.1.1651278267
The issue was not related with X code or node version but it was related to one the npm package I was using which was ibm_db and only if you have the mac monterey os.
Follow these step if you have this package installed to rectify the error.
Delete ibm_db package from your project and delete package-lock.json as well.
Install latest ibm_db package currently 2.8.1. Even if it does not resolve the error, do the last step.
Go to node_modules/ibm_db/installer/clidriver/lib and rename the file libstdc++.6.dylib to anything like libstdc++.7.dylib
You can find detailed discussion here
https://github.com/ibmdb/node-ibm_db/issues/824
https://github.com/ibmdb/node-ibm_db/issues/801
Hopefully the issue will be resolved. Thanks
i am new to ionic and i start basic tabs project using ionic cli. Everything is working fine, except when i tried "ionic cordova run android" command with redmi note 4 giving following error.
Error: Failed to execute shell command "input,keyevent,82"" on device: Error: adb: Command failed with exit code 137
it is working fine on redmi note 3, follow is log from terminal, Any help would be appreciated
[INFO] Running app-scripts build: --platform android --target cordova
[23:22:39] build dev started ...
[23:22:39] clean started ...
[23:22:39] clean finished in 6 ms
[23:22:39] copy started ...
[23:22:39] deeplinks started ...
[23:22:39] deeplinks finished in 64 ms
[23:22:39] transpile started ...
[23:22:45] transpile finished in 5.99 s
[23:22:45] preprocess started ...
[23:22:45] copy finished in 6.38 s
[23:22:46] preprocess finished in 229 ms
[23:22:46] webpack started ...
[23:23:08] webpack finished in 22.92 s
[23:23:08] sass started ...
[23:23:12] sass finished in 3.52 s
[23:23:12] postprocess started ...
[23:23:12] postprocess finished in 11 ms
[23:23:12] lint started ...
[23:23:12] build dev finished in 32.98 s
> cordova run android --device
ANDROID_HOME=/home/rogers/android-sdk
JAVA_HOME=/usr/lib/jvm/java-8-oracle
Subproject Path: CordovaLib
[23:23:18] lint finished in 5.77 s
The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead.
at build_rbfqc9qtl315khhol1quvz1g.run(/home/rogers/workspace/practice/myApp/platforms/android/build.gradle:141)
The JavaCompile.setDependencyCacheDir() method has been deprecated and is scheduled to be removed in Gradle 4.0.
Incremental java compilation is an incubating feature.
The TaskInputs.source(Object) method has been deprecated and is scheduled to be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty() instead.
:preBuild UP-TO-DATE
:preDebugBuild
UP-TO-DATE
:checkDebugManifest
:CordovaLib:preBuild UP-TO-DATE
:CordovaLib:preDebugBuild UP-TO-DATE
:CordovaLib:checkDebugManifest
:CordovaLib:prepareDebugDependencies
:CordovaLib:compileDebugAidl UP-TO-DATE
:CordovaLib:compileDebugNdk UP-TO-DATE
:CordovaLib:compileLint UP-TO-DATE
:CordovaLib:copyDebugLint UP-TO-DATE
:CordovaLib:mergeDebugShaders UP-TO-DATE
:CordovaLib:compileDebugShaders
UP-TO-DATE
:CordovaLib:generateDebugAssets
UP-TO-DATE
:CordovaLib:mergeDebugAssets
UP-TO-DATE
:CordovaLib:mergeDebugProguardFiles
UP-TO-DATE
:CordovaLib:packageDebugRenderscript
UP-TO-DATE
:CordovaLib:compileDebugRenderscript
UP-TO-DATE
:CordovaLib:generateDebugResValues
UP-TO-DATE
:CordovaLib:generateDebugResources UP-TO-DATE
:CordovaLib:packageDebugResources
UP-TO-DATE
:CordovaLib:processDebugManifest
UP-TO-DATE
:CordovaLib:generateDebugBuildConfig
UP-TO-DATE
:CordovaLib:processDebugResources UP-TO-DATE
:CordovaLib:generateDebugSources UP-TO-DATE
:CordovaLib:incrementalDebugJavaCompilationSafeguard
UP-TO-DATE
:CordovaLib:compileDebugJavaWithJavac
UP-TO-DATE
:CordovaLib:processDebugJavaRes UP-TO-DATE
:CordovaLib:transformResourcesWithMergeJavaResForDebug UP-TO-DATE
:CordovaLib:transformClassesAndResourcesWithSyncLibJarsForDebug
UP-TO-DATE
:CordovaLib:mergeDebugJniLibFolders
UP-TO-DATE
:CordovaLib:transformNative_libsWithMergeJniLibsForDebug UP-TO-DATE
:CordovaLib:transformNative_libsWithSyncJniLibsForDebug UP-TO-DATE
:CordovaLib:bundleDebug
UP-TO-DATE
:prepareOrgApacheCordovaCordovaLib630DebugLibrary
UP-TO-DATE
:prepareDebugDependencies
:compileDebugAidl
UP-TO-DATE
:compileDebugRenderscript
UP-TO-DATE
:generateDebugBuildConfig
UP-TO-DATE
:generateDebugResValues
UP-TO-DATE
:generateDebugResources UP-TO-DATE
:mergeDebugResources
UP-TO-DATE
:processDebugManifest
UP-TO-DATE
:processDebugResources
UP-TO-DATE
:generateDebugSources
UP-TO-DATE
:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
:compileDebugJavaWithJavac
UP-TO-DATE
:compileDebugNdk
UP-TO-DATE
:compileDebugSources UP-TO-DATE
:mergeDebugShaders UP-TO-DATE
:compileDebugShaders UP-TO-DATE
:generateDebugAssets
UP-TO-DATE
:mergeDebugAssets
UP-TO-DATE
:transformClassesWithDexForDebug
UP-TO-DATE
:mergeDebugJniLibFolders
UP-TO-DATE
:transformNative_libsWithMergeJniLibsForDebug UP-TO-DATE
:processDebugJavaRes
UP-TO-DATE
:transformResourcesWithMergeJavaResForDebug
UP-TO-DATE
:validateSigningDebug
:packageDebug
UP-TO-DATE
:assembleDebug
UP-TO-DATE
:cdvBuildDebug UP-TO-DATE
BUILD SUCCESSFUL
Total time: 3.045 secs
Built the following apk(s):
/home/rogers/workspace/practice/myApp/platforms/android/build/outputs/apk/android-debug.apk
ANDROID_HOME=/home/rogers/android-sdk
JAVA_HOME=/usr/lib/jvm/java-8-oracle
Skipping build...
Built the following apk(s):
/home/rogers/workspace/practice/myApp/platforms/android/build/outputs/apk/android-debug.apk
Using apk: /home/rogers/workspace/practice/myApp/platforms/android/build/outputs/apk/android-debug.apk
Package name: io.ionic.starter
Error: Failed to execute shell command "input,keyevent,82"" on device: Error: adb: Command failed with exit code 137
[ERROR] An error occurred while running cordova run android --device (exit code 1).
this is a Xiaomi "Security" issue. You have to activate the "USB Debugging (Security settings)" in the developer options.
I hope this works for you as it worked for me :D
Turn On these both as shown in the Screenshot.
For MI phones dont't forget to enable USB debugging (Security settings)
For MI phones dont't forget to enable
USB debugging (Security settings)
First remove the android platform and add it again.
Use these 2 commands.one by one
1.ionic platform remove android.
2.ionic platform add android.
It works for me.
Since we're constantly reinstalling the app by copying it from the Ionic CLI to the device, there are couple of issues that I found that resulted the above's issue:
The app's version is lower than the one you try to install
uninstall the app - and try again
Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user] means that the USB debugging is either off or on, but the "installed via USB" is off ...
if you don't have enough space on the phone make sure to make a space on your storage
check the storage of the device if have enough storage is good.
else free some space.
after that re-run the command if isn't become successful, please check another device, the problem is that device
I install Erl7.3 and rabbitmq-server 3.6.2. I using Win7 32bit. After installing when I run 'rabbitmq-server' command it gives:
ERROR: node with name "rabbit" already running on "admin-PC"
When I run 'net stop RabbitMQ && net start RabbitMQ' it stopped RabbitMQ service and restarted successfully.
After that When I run "rabbitmq-plugins enable rabbitmq_management", it gives following errors and nothing is shown at http://localhost:15672:
Plugin configuration unchanged.
Applying plugin configuration to rabbit#admin-PC... failed.
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
[{file,"src/rabbit_misc.erl"},{line,817}]},
{rabbit_misc,'-all_module_attributes/1-fun-0-',3,
[{file,"src/rabbit_misc.erl"},{line,837}]},
{lists,foldl,3,[{file,"lists.erl"},{line,1262}]},
{rabbit_boot_steps,find_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,40}]},
{rabbit_boot_steps,run_boot_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,26}]},
{rabbit,start_apps,1,[{file,"src/rabbit.erl"},{line,451}]},
{rabbit_plugins,ensure,1,
[{file,"src/rabbit_plugins.erl"},{line,52}]}]}
For your information, I set environmental variables as:
'Variable name: ERLANG_HOME', 'Variable value: C:\Program Files\erl7.3';
'Variable name: RABBITMQ_SERVER', 'Variable value: C:\Program Files\RabbitMQ Server\rabbitmq_server-3.6.2'
and system path "%ERLANG_HOME%;;%RABBITMQ_SERVER%\sbin"
How to resolve this errors?
rabbitmq management plugin needs the cryptopakage to work.
see:
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
Try to use the Erlang 18.3 version.
EDIT
After installing when I run 'rabbitmq-server' command it gives:
ERROR: node with name "rabbit" already running on "admin-PC"
This is normal since rabbitmq-server starts the server, but you have rabbitmq installed and running as windows service.
And you should use the 64 bit version
I have trouble on updating tizen-2.1 on my test device
I follow manual step by step, but some errors when I use lthor tool.
Can you give me some insight?
my environment
current tizen version on test device => 2.0
ubuntu 13.04 (on vmware 9)
modemmanager off
Error Message:
line 345: failed to read signature bytes
line 629: handshake failed
line 958: failed to open port (null)
Unfortunatelly, sometimes it's needed to uninstall modemmanger at all:
sudo apt-get purge modemmanager
Also VMWare may be at the bottom of your problem.
please follow these steps
I updated my device by following these steps.
https://wiki.tizen.org/wiki/Flash_Tizen_2.1_Image_to_Reference_Device