I am having an issue with a custom filter plugin, and importing a dependency. Can anyone please help me? I get "Trying to load the X filter plugin resulted in this error: no such file to load -- memcache". The code does "require 'memcache". This is available as if I do that in any other script and run it on the CLI, it works, just not when logstash runs it? Does it use some bundled ruby or smth with a different import path? Its 1.4.2 on Debian, if that matters. Driving me insane (Im not a ruby hacker, so im spinning my wheels a bit).
Related
I have been using a google colab template for iterative LQR that uses the Pydrake, however, it seems like the code repository is removed and I can't reinstall it on google Colab:
try:
import pydrake
import underactuated
except ImportError:
!curl -s https://raw.githubusercontent.com/RussTedrake/underactuated/master/scripts/setup/jupyter_setup.py > jupyter_setup.py
from jupyter_setup import setup_underactuated
setup_underactuated()
# Setup matplotlib backend (to notebook, if possible, or inline).
from underactuated.jupyter import setup_matplotlib_backend
plt_is_interactive = setup_matplotlib_backend()
File "/content/jupyter_setup.py", line 1
404: Not Found
^
SyntaxError: invalid syntax
I tried clicking this link https://raw.githubusercontent.com/RussTedrake/underactuated/master/scripts/setup/jupyter_setup.py, and the page is not found... everything was working fine yesterday
Sorry. You're correct... I updated it this morning, and don't have a good deprecation policy in place on that repo, and this setup script is two versions ago. The path you want is https://raw.githubusercontent.com/RussTedrake/underactuated/master/setup/jupyter_setup.py
(remove the script from the directory). But if you look at that file, you'll see that even that is pointing to an updated setup script which you might want to point to.
This is actually all good news... we are on the path to a much better solution. You can now just pip install drake on colab (see the drake installation guide). Once I land the pip install underactuated (probably in time for my Spring offering of the class), then all of that nasty setup will be gone.
I get the following when I try to run Spyder from a Python 3.7 32 bit environment:
I don't really know how resolve this so any help would be greatly appreciated.
I read the below fix but I am not getting any Windows like in the below to try it.
Spyder 5 No QCoreApplication instance found. Application patches not applied
Seems like the error is related with DLLs required for the ssl module:
import _ssl # if we can't import it, let the error propagate
ImportError: DLL load failed: The specified module could not be found.
To fix that you will need to either make available for your python installation the missing DLL (probably libssl.dll and libcrypto.dll) or maybe try to use a python version bellow 3.7.
Also, the message Spyder 5 No QCoreApplication instance found. Application patches not applied... is just a warning as described in one of the responses here: https://stackoverflow.com/a/66979214/15954282
I've used the Vitis docker tool container using only the CPU and Conda worked fine; however, when I want to use the GPU version for docker, I get the below error. I tried building the environment twice and each time it has failed to import the right libraries.
(vitis-ai-caffe) sam#Itec:~/cf_resnet50$ vai_q_caffe quantize -model float/trainval.prototxt -weights float/trainval.caffemodel
vai_q_caffe: error while loading shared libraries: libprotobuf.so.21: cannot open shared object file: No such file or director
How might I resolve this error? I will be happy to receive any help.
With version 1.0.0 there is an issue in the docker with the protobuf library version. It can be resolved by patching the conda_requirements.txt. To do so, open the conda_requirements.txt in a text editor and add the following two lines, then build the GPU docker:
libprotobuf==3.10.1
protobuf==3.10.1
I'm trying to find a Pry Deubgger equivalent on Groovy.
I found a good enough project named groovy-debugger and updated it's dependencies to run against groovy 2.3.1 which comes with Grails 2.4.0.
If I open a groovysh just a blinking cursor will be shown which does not accept any input.
I tried to get the input stream and output stream of a current grails console, but it does not help.
Anyone can help me setup my beloved REPL-driven development environment on Groovy.
So using Grails 2.4.0 I created a new project and started the shell with grails shell and it was able to accept input with no problem. This is with Mac OS X. What operating system are you running?
I have recently started to work with grails. I was able to create applications and generate stuff. Yesterday I wanted to resume my work, after a little break and ran into the following error, when trying to create a new project:
Command terminated with an exception:
org.grails.ide.eclipse.longrunning.client.GrailsProcessDiedException: Grails process died
(see details for partial output)
Grails process died
------System.out:-----------
------System.err:-----------
This error only occurs when I use the SpringSourceTool, if I try using the command line it works fine. My first reaction was to change the java version from 1.8 to 1.7, but that didn't help. My environment variables look like this (I am running Fedora Linux 19)
JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.0.x86_64
GRAILS_HOME=/home/peer/grails/grails-2.3.0
They are also included in the PATH variable.
Can anybody help? Thanks, Peer
This is a known issue in STS:
https://issuetracker.springsource.com/browse/STS-3277
A work-around is provided in the link.
For anyone pulling their hair out trying to create a grails project using the STS extension for Grails, here is my setup and following is what I did to get it working:
-- OSX 10.8.4 Build 12E3067 --
-- STS Version 3.4.0 --
-- Grails 2.3.3 (installed separately to STS) --
Fresh installed STS 3.4.0
I *de*selected the Preferences/Groovy/Compiler/Enable checking for mismatches between
project and workspace Groovy compiler levels
I ONLY selected the Grails Support option when installing the extensions (nothing else)
Restart STS 3.4.0 (i.e. restart eclipse)
I then pointed my Grails project to my existing Grails 2.3.3 installation
Make sure that the environment variable GRAILS_HOME is set and exported in the same
shell from which you invoke STS otherwise you will get a process termination error in
Eclipse (STS)
This worked.