I'm trying to use EIP 198 (https://github.com/ethereum/EIPs/blob/master/EIPS/eip-198.md) locally on ganache-cli, has anyone done that?
I keep getting an unknown opcode error.... I've ran ganache-cli with the ganache-cli -k byzantium argument already :\
The contract I'm specifically trying to deploy is: https://ropsten.etherscan.io/address/0x0feedd6091b9448b376ebb7f4d756b6f823439db#contracts
Turns out all I has to do was run it with ganache-cli -k=petersburg as I was running solidity>=0.5.0
Related
I am working on a Xilinx DPU project and was able to train, freeze and quantize my model with the given tools and tensorflow. Now I wanted to use the dnnc-dpu1.4.0 compiler to generate an *.elf file. When executing this command:
dnnc-dpu1.4.0 \
--parser=tensorflow \
--frozen_pb=./quantize_results/deploy_model.pb \
--dpu=1152FA \
--cpu_arch=arm64 \
--output_dir=compile \
--save_kernel \
--mode normal \
--net_name=mnist
it throws this error:
terminate called after throwing an instance of 'invalid_random_param'
what(): Random Param Exception Happened
./compile.sh: line 22: 7602 Aborted (core dumped) dnnc-dpu1.4.0 --parser=tensorflow
--frozen_pb=./quantize_results/deploy_model.pb --dpu=1152FA --cpu_arch=arm64 --output_dir=compile --save_kernel --mode normal --net_name=mnist
I am not sure what to do because this error is very cryptic. It doesn't tell me where those parameters were used or occur, and I won't be able to do something about it. The model works perfectly fine, at least the layers and so on, as I was able to deploy the model itself before. The only thing I changed was the data set and output node count. What could this be? Why is there no extensive error description anywhere?
This is my output for dnnc-dpu1.4.0 --version:
dnnc version v2.05
DPU Target : v1.4.0
Build Label: Jun 24 2019 13:40:08
Copyright #2019 Xilinx Inc. All Rights Reserved.
So I should be up-to-date.
Could anybody help me? This is the last step before I'd be able to deploy my model on the Xilinx DPU. Thank you very much!
Update 1
I posted the same question in the Xilinx Community Forum already.
Update 2
Also, I already found this post on the Xilinx Community Forum, but this does not seem to have a solution to my problem. I can't update the DNNDK, an since I already compiled my model successfully and did no change anything with it, this "solution" seems to be non-applicable to my problem.
I'm trying to run truffle in a linux virtual machine with a windows 10 host. When I run truffle init this is the error that I get...
DownloadingError: write EPROTO 140718189083520:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:827:
at _errnoException (util.js:1022:11)
at WriteWrap.afterWrite (net.js:880:14)
I'm not really sure what's causing the error or how to solve it. Any advice would be appreciated. Thanks in advance!
This seems to be an issue with proxies.
I suggest you update your node environment to at least v10.16.0.
If that doesn't work try the answers to this other post.
npm gets stuck on fetchMetadata -> network
I use feathers for some months now and I already created and used several services. The app is generated with feather/cli command: 'feathers generate app'.
Today I tried to generate a new service with the usual command:
feathers generate service
only to get the error:
× This version of the generator will only work with Feathers Buzzard (v3) and up. Please runfeathers upgradefirst.
Fine. Run the upgrade. Got new error:
throw new Error('It looks like#feathersjs/feathersis already a dependency. I can not run the upgrade again.');
^
checked the version: is 3.9.0
Uninstalled/re-installed feathers/cli
Nothing works. Not sure what I broke as I did not (remember to) upgrade anything since a couple of days ago when I created the last service. Feathers was not updated in the last 4 months.
I tried googling my error but it seems like nobody else has this problem so it has to be something I've done.
Any suggestions?
LE: I have in package.json dependencies:
"#feathersjs/errors": "^3.3.6",
"#feathersjs/express": "^1.3.1",
"#feathersjs/feathers": "^3.3.1",
"#feathersjs/socketio": "^3.2.9",
"feathers-knex": "^5.0.7",
"feathers-memory": "^3.0.2",
"feathers-rest": "^1.8.1",
"feathers": "^2.2.4",```
This error will be shown if you still have the feathers module in your dependencies in your package.json. If #feathersjs/feathers is already included as well you can just remove the feathers dependency (after making sure it is not used anywhere else in your application which it shouldn't).
I'm trying to deploy/migrate contract to rinkeby network, while using command:
truffle deploy --reset --network=rinkeby
It loads the keys and afterwards throws error:
C:\Users\marti\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\truffle-provider\wrapper.js:26
var originalSendAsync = provider.sendAsync.bind(provider);
TypeError: Cannot read property 'bind' of undefined
I'm able to run truffle develop without any issues
I'm also using:
truffle-hdwallet-provider
zappelin-solidity
Okay so the issue was comming from the truffle-hdwallet-provider version.
changing the ver from : 1.0.0-web3one.2
to : 0.0.6
solved the issue
Seeing this error quite frequently.
Jruby 1.7.13
Ubuntu 14.
Sun Java 8 _05
ps -ef command for the process:
java -Xmx786m -Xss2048k -Djffi.boot.library.path=/home/ubuntu/server/tools/jruby/lib/jni -Xmn128m -server -Xbootclasspath/a:/home/ubuntu/server/tools/jruby/lib/jruby.jar -classpath : -Djruby.home=/home/ubuntu/server/tools/jruby -Djruby.lib=/home/ubuntu/server/tools/jruby/lib -Djruby.script=jruby -Djruby.shell=/bin/sh org.jruby.Main bin/rails s -p4005 -e production
Any idea what is causing that error infrequently.
Java::JavaLang::RuntimeException (com.headius.invokebinder.InvalidTransformException: java.lang.IllegalAccessException: no such method: rubyjit.ContactSerializer$$fast_attributes_a0671ee9e02931c7660594220ffed4d4fc58cad5681842940.__file_(ContactSerializer$$fast_attributes_a0671ee9e02931c7660594220ffed4d4fc58cad5681842940,ThreadContext,IRubyObject,Block)IRubyObject/invokeStatic):
org.jruby.runtime.invokedynamic.InvocationLinker.createRubyHandle(InvocationLinker.java:1689)
org.jruby.runtime.invokedynamic.InvocationLinker.access$900(InvocationLinker.java:75)
org.jruby.runtime.invokedynamic.InvocationLinker$RubyCallGenerator.generate(InvocationLinker.java:715)
org.jruby.runtime.invokedynamic.InvocationLinker.tryDispatchDirect(InvocationLinker.java:765)
org.jruby.runtime.invokedynamic.InvocationLinker.getTarget(InvocationLinker.java:775)
org.jruby.runtime.invokedynamic.InvocationLinker.invocationFallback(InvocationLinker.java:137)
rubyjit.ActiveModel::Serializer$$attributes_dbeb427ba2b0518d676c0a687aeb474a438bbc8b681842940.chained_0_rescue_1$RUBY$SYNTHETIC__file_(active_model_serializers (0.8.1) lib/active_model/serializer.rb:454)
rubyjit.ActiveModel::Serializer$$attributes_dbeb427ba2b0518d676c0a687aeb474a438bbc8b681842940.file(active_model_serializers (0.8.1) lib/active_model/serializer.rb)
rubyjit.ActiveModel::Serializer$$serializable_hash_77c90db1574839863dc0d7ab15cb761d318d3fad681842940.__file_(active_model_serializers (0.8.1) lib/active_model/serializer.rb:478)
rubyjit.ActiveModel::Serializer$$serializable_hash_15164681ef3759650116133c60c86faa4d0da16f681842940.file(active_model_serializers (0.8.1) lib/active_model/serializer.rb:360)
rubyjit.ActiveModel::ArraySerializer$$serializable_array_3e75f1b3d701c37c0dd6c09012f195834f37a85e681842940.block_0$RUBY$__file_(active_model_serializers (0.8.1) lib/active_model/array_serializer.rb:89)
rubyjit$ActiveModel::ArraySerializer$$serializable_array_3e75f1b3d701c37c0dd6c09012f195834f37a85e681842940$block_0$RUBY$__file_.call(rubyjit$ActiveModel::ArraySerializer$$serializable_array_3e75f1b3d701c37c0dd6c09012f195834f37a85e681842940$block_0$RUBY$__file_)
org.jruby.runtime.CompiledBlock19.yield(CompiledBlock19.java:135)
org.jruby.runtime.Block.yield(Block.java:142)
org.jruby.RubyArray.collect(RubyArray.java:2399)
org.jruby.RubyArray.map19(RubyArray.java:2412)
org.jruby.RubyArray$INVOKER$i$0$0$map19.call(RubyArray$INVOKER$i$0$0$map19.gen)
org.jruby.internal.runtime.methods.JavaMethod$JavaMethodZeroBlock.call(JavaMethod.java:458)
would be great if you can come up with a piece of script where this gets reproduced (and submit it to JRuby's issue tracker) as this is invoke-dynamic related, which gets turned on for you due Java 8.
work-around would be (unless you get other advice what the failure actually means - if it's fine to live with) to disable indy :
java -Djruby.compile.invokedynamic=false -Xmx786m -Xss2048k ...
or if you're about to use the jruby executable :
jruby -Xcompile.invokedynamic=false -S ...
both can be added to their corresponding XXX_OPTS environment variable