Which version of sl4j is used in Jetty8. There is no sl4j provided with the Jetty8.1 distribution and several attempts to get a compatible version of sl4j for this has failed. Is there a link from where this compatible sl4j can be downloaded. As of now sl4j in the current setup that I have created sl4j is not used at all. But I want to use this.
Define in jetty-project pom.xml in version 8.0.0.M3 :
<slf4j-version>1.5.11</slf4j-version>
The slf4j version is 1.6.1 as you can see in the POM for version 8.1.7. Use maven and you won't have problems with dependencies.
Related
For example, how can I list available GDAL library versions ?
They are not listed on VCPKG packages website neither by vcpkg search gdalcommand.
Try this! it is a quick fix until vcpkg supports pkgs version listing. https://github.com/hamaney/vcpkg_version_finder.
on a related note:
to look up a package by name and get the latest available version of it use vcpkg search <pkg name>
UPDATE SEP-11-2021:
I just found out that you can use the experimental flag x-history. for example vcpkg x-history <pkg name> (you might need an internet connection the first time you run this command).
You can use https://vcpkg.link/ in order to find all the versions of a package and when it got released (e.g. https://vcpkg.link/ports/gdal/versions for gdal). Besides, you can also see from which version a given feature has been introduced by looking at the overview of a package.
Disclosure: I'm the creator of the platform.
is there possibility how to install older version of packages by using vcpkg install?
I found that there is a file in versions/baseline.json, but even if I change the version of the package there, it always install the newest one.
Maybe https://github.com/microsoft/vcpkg/blob/master/docs/specifications/versioning.md is what you are looking for. Be aware you need to pass an additional flag to vcpkg to activate that feature. It also only works in manifest mode and not in classic mode.
I would like to deploy and test my Lambda function, but, every time I try to do that I am getting following error message:
2019-11-11 13:25:33 Mounting /tmp/tmphebm3s_4 as /var/task:ro,delegated inside runtime container
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libopencv_dnn.so.4.1)
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libopencv_video.so.4.1)
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libopencv_objdetect.so.4.1)
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libopencv_features2d.so.4.1)
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libopencv_imgproc.so.4.1)
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libopencv_core.so.4.1)
/var/task/bin/inference: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/lib/libinference_engine.so)
/var/task/bin/inference: /lib64/libdbus-1.so.3: no version information available (required by /opt/lib/libatk-bridge-2.0.so.0)
^C/var/task/bin/inference: /lib64/libdbus-1.so.3: no version information available (required by /opt/lib/libatspi.so.0)
Makefile:85: recipe for target 'run-inference' failed
Note that inference is name of my Lambda functions binary.
I found about this link: https://aws.amazon.com/premiumsupport/knowledge-center/lambda-linux-binary-package/ that lets me use Amazon Linux box in order to create deployment package adequate for Lambda function execution environment.
My plan was to copy code to EC2 instance and build it with GLIBC version installed on it. I think that this would fix issue mentioned above.
Problem is that, once I SSH to EC2 instance, how do I copy my code to it and then build it? I am not an expert in linux so this is kinda confusing to me.
Thanks in advance!
I have just answered a similar question that addresses that issue you had, in which was the same issue I had earlier today. Please look at:
How can I use environmental variables on AWS Lambda?
In addition to looking there, please note that you will have to pack a layer into your AWS Lambda Function in which will need to have the correct LIB files -- "libm.so.6" is one for example -- in the lib folder of your layer. After that, you will need to set up the environmental variable, as explained in the link above, so that the correct lib file of your layer is used at runtime and thus your code runs successfully.
In order to get the correct LIB file, I would suggest googling more, and also trying to run your code in conda. My project was developed in a conda environment, and when I translated into a virtualenv so that I could package into a Layer and then upload to AWS Lambda, I noticed that I was getting that error too. I then grabbed the correct lib file from either (don't remember now) the lib folder of my conda environment, or the lib folder of the conda installation directory, and I placed in the lib folder of my layer package. After that, I stll had to set the environment variable so that those specific lib files would load and be linked to the python runtime.
The problem here lies in incompatibility between the version of OpenCV that you are trying to use and Amazon Linux, the OS that runs it. Basically, you are trying to use OpenCV compiled for a different system and it can't run.
To solve this, you need to build OpenCV for Amazon Linux and for the current version of the programming language that you use. Here is a repository for Python 3.7 that I used. Please note, that it will not run correctly, unless you comment out all of 3.8 installation and add a RUN pip3.7 install --upgrade pip line into the Dockerfile before RUN pip3.7 install -r requirements.txt <...>.
I was having this error while creating the Rust binary to deploy in an AWS Lambda.
I solved it by using cross as suggested in this GitHub comment.
I performed these two steps to solve the issue:
Install cross: cargo install cross
Compile the project using cross: cross build --release --target x86_64-unknown-linux-gnu
I am trying to use HtmlAgilityPack nuget package in netcoreapp1.0 (I am restricted to this version since AWS Lambda supports only it). Which version of the HtmlAgilityPack package should I use? The point is .NETStandardLibrary 1.6.0 is only compatible with netcoreapp1.0 but I don't see any version of HtmlAgilityPack which would be compatible with .NETStandardLibrary 1.6.0. The minimum version I can see is .NETStandardLibrary 1.6.1 but this is for netcoreapp1.1.
From a .NET Standard API prospective nothing changed between NETStandard.Library 1.6.1 and 1.6.0. We only bumped the version of the meta-package so that we could pull in newer versions of the dependent packages which contain implementation fixes but no real new API surface for NS1.6.
See the issue #171 in DotNet standard repo What's the change in NetStandard.Library 1.6.1 vs 1.6.0?
Even if there will be no HtmlAgilityPack compatible (or build against) netstandard1.6, but there is a netstandard1.6.1 I would just build it for myself by replacing netstandard v1.6.1 nuget package with netstandard v1.6 package ( HtmlAgilityPack is open source - right :) ).
Most importantly there is no netstandard1.6.1, it was never released or even worked on, v1.6.1 stands only for the version of NETStandard.Library NuGet package.
I just downloaded biicode and tried to follow the getting started instructions but received an error about the Cmake 3.0 or higher being required.
However, ubuntu 14.4 uses "cmake version 2.8.12.2"
Is there a way to use biicode with 2.8 or am I stuck installing the newer version of CMake?
TIA!
No, biicode requires cmake > 3.0. There is a setup command that helps installing it:
$ bii setup:cpp
This will install CMake >3.0 in /home/user/biicode_env, and add it to the path, so it doesnt interfere/overwrite your current 2.8 installation. Biicode needs that executing "cmake" in the console actually uses 3.0, so it should be first in the path. You can manage it very easily in two different ways, with a symbolic link (/usr/bin) that you redirect as needed or adding/removing an entry in the path before executing biicode.
This is a different thing, but I woiuld like to say that I have migrated existing projects from cmake 2.8 to 3.0 without any problems, and 3.0 runs great and has useful new features. So I would recommend regular cmake users to upgrade if possible.
No, there isn't any way to change this requirement because internal biicode CMake has features, like the use of INTERFACE libraries, which are only available on CMake 3.0 or later. However, don't worry about upgrading CMake version, this one always keeps a exhaustive compatibility with older versions ;)