DNNC throws error " terminate called after throwing an instance of 'invalid_random_param' " - deep-learning

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.

Related

When I create a sentinel of redis-plus-plus, an exception is raised

Please forgive me for not speaking English well.
I am trying to use the redis sentinel function.
When I create a sentinel of redis-plus-plus, an exception is raised.
Exception occurs when Sentinel is created as shown in the code below.
image
Exceptions are as follows.
image
I've also asked git about the issue.
https://github.com/sewenew/redis-plus-plus/issues/342
Please help me.
Environment:
OS: windows7
Compiler: visual studio 2022 / unicode
hiredis version: master (date: 2022-2-2 2:10, commit:f8de9a4)
redis-plus-plus version: master (date: 2022-2-8 23:30, commit:244e8cb)
c++ version : 17

I have a problem importing a Bit compiler. How can I resolve the following error?

I'm working with 'Bit' to create reusable React components. I have created my 'Bit' account and followed tutorials on the web to log on to Bit from the terminal and I have initialized the Bit workspace. I am encountering the following error when importing the React compiler.
$ bit import bit.envs/compilers/react --compiler
fatal: unable to connect to a remote legacy SSH server from Harmony client
Any advice would be appreciated.
the compiler flag was removed in 0.0.537
harmony became default in 0.0.438 (so legacy was last default in 0.0.437)
but ... if you try to run this on 0.0.437 now, you're likely to get an error:
server responded with: "Please update your Bit client.
For additional information: https://docs.bit.dev/docs/installation#latest-version"
the best place to get bit.dev answers is their community Slack here: https://join.slack.com/t/bit-dev-community/shared_invite/zt-o2tim18y-UzwOCFdTafmFKEqm2tXE4w.

Getting logs/more information during start-build command execution

Jenkins pipeline is building Docker images. OpenShift plugin(s) are used for the same.
An example command:
openshift.selector(BUILD_CONFIG_NAME, "${appBcName}").startBuild("--from-dir=${artifactPath}", '--wait','--follow')
While this works smoothly most of the time, whenever this command fails due to some underlying platform issues, almost no information is seen in the Jenkins build job console:
[Pipeline] }
[start-build:buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd] ............................................................
[start-build:buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd] Uploading finished
[start-build:buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd] Error from server (BadRequest): unable to wait for build amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd-857 to run: timed out waiting for the condition
[Pipeline] }
ERROR: Error running start-build on at least one item: [buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd];
{err=, verb=start-build, cmd=oc --server=https://api.scp-west-zone02-z01.net:6443 --certificate-authority=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt --namespace=sb-1166-amld5-car-service-se --token=XXXXX start-build buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd --from-dir=./build/libs --wait --follow -o=name , out=Uploading directory "build/libs" as binary input for the build ...
............................................................
Uploading finished
Error from server (BadRequest): unable to wait for build amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd-857 to run: timed out waiting for the condition
, status=1}
[Pipeline] // catchError
I need more verbosity, detailed error information. I checked the start-build command reference, and I thought --build-loglevel [0-5] might help here. When I used it, I got a warning that since I am using source type as 'Binary' in the BuildConfig, logging isn't supported(seriously???)
NOTE: the selector returned when -F/--follow is supplied to startBuild() will be inoperative for the various selector operations.
Consider removing those options from startBuild and using the logs() command to follow the build output.
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] WARNING: Specifying --build-loglevel with binary builds is not supported.
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] WARNING: Specifying environment variables with binary builds is not supported.
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] Uploading directory "build/libs" as binary input for the build ...
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] ..
How do I get more logs, info. while executing the start-build command?
I was facing the same problem, I just used something like:
def build = openshift.selector(BUILD_CONFIG_NAME, "${appBcName}").startBuild("--from-dir=${artifactPath}", '--wait','--follow')
build.logs('-f')
And so far it seems to work, I got the logs from my openshift build in my Jenkins pipeline. Now I'll try to get the logs only if build does not Complete, to reduce the overall logs.
(for future searchers like me ^^)

apache drill: "no current connection" error and "could not find or load main class sqlline.sqlline" error

I am using JDK: 1.8.0.281 and Drill: 1.18.0 on m1 Mac.
I cannot start drill downloaded from https://drill.apache.org/download/ directly. It says
could not find or load main class sqlline.sqlline. So I refer to https://github.com/julianhyde/sqlline/issues/69, download and compile sqlline and add these two lines
BINPATH=/Users/fields/Repositories/sqlline-sqlline-1.9.0/bin
exec java -cp $BINPATH/../target/sqlline-1.9.0-jar-with-dependencies.jar sqlline.SqlLine "$#"
to the beginning of drill/bin/sqlline. Then I start drill-embedded and get no current connection every time I enter a query.
Please help me identify the problem. Thanks a lot!!!

java.lang.IllegalAccessException: no such method: rubyjit.<name>Serializer$$_fast_attributes

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