I've been working with AWS lambdas for a few months. I was working with a lambda and it was fine at the end of the day. I came back to work on it the next day, and I can't get Visual Studio to even start the application using the Mock Lambda Test Tool.
I ended up creating an empty lambda that just returns the input (the standard project code that AWS gives you as a template) and that won't even run. I hit the play button to star the Mock Lambda Test Tool, it looks like it will run for a couple seconds, then it closes down. The command window does not even pop up.
This is the code from the template project.
public string FunctionHandler(string input, ILambdaContext context)
{
return input?.ToUpper();
}
This is all I get in the output window of VS:
The target process exited without raising a CoreCLR started event.
Ensure that the target process is configured to use .NET Core. This
may be expected if the target process did not run on .NET Core. The
program '[16700] dotnet-lambda-test-tool-2.1.exe: Program Trace' has
exited with code 0 (0x0). The program '[16700]
dotnet-lambda-test-tool-2.1.exe' has exited with code -2147450726
(0x8000809a).
I have tried re-installing the AWS toolkit, and also tried re-installing Visual Studio. This is an issue with VS 2017 and VS 2019. I just installed 2019 to see if that would fix the issue. Any help would be appreciated.
I came to this question having the very same issue. After installing AWS Toolkit I found that the lambda test tool was not installed and therefore I got the same error just as the OP. The only difference is that I was targeting .Net Core 3.1 and therefore I needed amazon.lambda.testool-3.1. However this answer should work for both scenarios.
Unfortunately I did not have the same luck as the OP of having a nice co-worker that could give me the files I needed. So, if this is also your case please continue reading.
In the official project site, which can be found here, there are the instructions to install the tools. It also says that installing the latest version of AWS Toolkit should be enough to have the tools installed (it was not in my case and probably in yours).
It says that in order to install the tools you should run the following commands:
dotnet tool install -g Amazon.Lambda.TestTool-3.1
or
dotnet tool install -g Amazon.Lambda.TestTool-2.1
depending on which tool you need.
However, running these commands fails with the following message:
The tool package could not be restored.
Tool 'amazon.lambda.testtool-2.1' failed to install. This failure may have been caused by:
* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET Core tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.
For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
And since the project is still in preview I just had to find the latest stable version in order to specify it in the command. For .net core 3.1 here is the nuget site, there I found version 0.10 to be the latest, so the command should look like:
dotnet tool install -g --version 0.10 Amazon.Lambda.TestTool-3.1
I have faced the same issue and when i tried to install dotnet-lambda-test-tool-3.1.exe using command prompt I got this issue:
Failed to create shell shim for tool 'amazon.lambda.testtool-3.1': Command 'dotnet-lambda-test-tool-3.1' conflicts with an existing command from another tool.
Tool 'amazon.lambda.testtool-3.1' failed to install.
And I did the following to fix issue
Deleted the dotnet-lamda-test-tool-3.1.exe from the installed folder (C:\Users%USERNAME%.dotnet\tools\dotnet-lambda-test-tool-3.1.exe)
Run dotnet tool install -g --version 0.10 Amazon.Lambda.TestTool-3.1 on cmd.
I have faced the same issue and got errors like "dotnet-lamda-test-tool-2.1.exe has exited with code.."
I did the following to fix the issue
Removed the dotnet-lamda-test-tool-2.1.exe from the installed folder
(C:\Users%USERNAME%.dotnet\tools\dotnet-lambda-test-tool-2.1.exe)
Removed the [amazon.lambda.testtool-2.1] folder as well
(C:\Users%USERNAME%.dotnet\tools\tools.store\amazon.lambda.testtool-2.1)
Installed dotnet tool from Developer command prompt using the command
[install -g Amazon.Lambda.TestTool-2.1]
Run the project. It is working
I have seen this issue many time on my system with dotnet-lambda-test-tool-6.0. Only one fix work for me
Remove dotnet-lambda-test-tool-6.0.exe from C:\Users\username.dotnet\tools
Open Command prompt from C:\Users\username.dotnet\tools
run command dotnet tool install -g Amazon.Lambda.TestTool-6.0
For anyone else that hits this same issue, it had to do with the the AWS toolkit install. I did not modify it, but somehow it was no longer working. I tried un-installing and re-installing, but it was still having issues running it. A co-worker sent me the exe and subdirectory that was setup on his machine under C:\Users\%user%.dotnet\tools. The exe is located in this directory, and there is another folder under .store for amazon.lambda.testtool-2.1. That directory had different folders and files than what I was able to install. So I copied in what he had and it worked. There might be a profile file associated to the tools install that points to these folders and files that might need to be modified. Since I was able to fix it with this, I didnt look any further into that.
I had the same issue with my .NET 6.0 lambda project. I installed the tool by executing dotnet tool install --global Amazon.Lambda.TestTool-6.0 --version 0.12.6 as suggested on https://www.nuget.org/packages/Amazon.Lambda.TestTool-6.0
Just ensure it is installed at %USERPROFILE%\.dotnet\tools\dotnet-lambda-test-tool-6.0.exe
I got the same issue with VS2019 with lambda design in 3.1 version and in Output window getting error
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.
Then checked the folder having multiple version of lambda-test-tool in path
C:\Users{username}.dotnet\tools
I removed all the lambda-test-tool and installed the required tool only with version 3.1 by command in developer command prompt:
dotnet tool install -g --version 0.10 Amazon.Lambda.TestTool-3.1
Then I can able to debug the lambda
I am attempting the installation of ESP-IDF toolchain for windows with the installer from here
However the installation fails with the exit-code=128.
Since I am a newbie I am not sure if I am missing something assuming the installer will take care of installation of all the dependencies
I am attaching the logs here for the reference
System Spec:
1.OS : windows 10
2. Processor : I7-8th Gen
If you have installed git and python (I think you do if you tried to use the windows installer beforehand), you can try to install the toolchain from the terminal.
Open a CMD (Win+R, cmd, Intro)
Create a new folder (be aware that ESP-IDF does not like spaces in the path)
2.1 mkdir C:\esp
2.2 cd C:\esp
Clone the repository from git into the current directory with:
git clone -b v4.2 --recursive https://github.com/espressif/esp-idf.git . <= don't forget the . at the end
Run install.bat
Once installed, you can run in the folder you project lives c:\esp\export.bat which will set the environment variables for you to use idf.py tool.
If you are trying to install ESP-IDF on Windows and still having issues, try the latest installer with some pre-install verification.
You can download here: IDF-Installer
Alternatively, you can try this tool: idf-env
On MacOS 10.15.5, running IntelliJ Ultimate 2020.2.2.
I am trying to build a test project with Gluon using GraalVM via the client-gradle-plugin(0.1.32). I've followed all the setup listed in the README and GraalVM's docs as follows:
Download the latest GraalVM for mac from here
Unpack the tar and sudo mv it to /Library/Java/JavaVirtualMachines
Added the following to .zshrc:
export PATH=$PATH:/Library/Java/JavaVirtualMachines/graalvm-ce-java11-20.2.0/Contents/Home/bin
export JAVA_HOME=/Library/Java/JavaVirtualMachines/graalvm-ce-java11-20.2.0/Contents/Home
export GRAALVM_HOME=$JAVA_HOME
Set my Project SDK to point to the same place as $GRAALVM_HOME (not sure this was needed?)
My project builds and runs just fine on the desktop, but I am now trying to target iOS. I got to the point where it was trying to find my iOS sdk so I was double checking my XCode setup to try and connect the dots.
Suddenly, when running sudo ./gradlew build nativeBuild I started getting the same error I had been stuck on for a long time:
GraalVM installation directory not found. Either set GRAALVM_HOME as an environment variable or set graalvmHome in the client-plugin configuration
If I echo $GRAALVM_HOME I get /Library/Java/JavaVirtualMachines/graalvm-ce-java11-20.2.0/Contents/Home so things seem like they're set up correctly. I've tried to reset everything from the IDE, the computer, the GraalVM install and I can't come up with a way to get back to where my nativeBuild gets past this point.
I was having some problem running SonarQube plugin and SonarLint on Visual Studio Code.
After installing the former or both plugins, I tried to run (following the tutorial...) the command SonarQube Inject: Create global config with credentials to servers which ended up with the following message command 'sonarqube-inject.analyzeProject' not found.
On windows type: Ctrl-Shift-P and then write Sonar. The editor will show the options to use.
Problem is coming from the plugin binary not being executable by default (at least on my Ubuntu 16.04 / VSCode 1.14).
I just needed to make it executable:
cd ~/.vscode/extensions/silverbulleters.sonarqube-inject-1.3.0/tools/sonarlint-cli/bin/
chmod u+x sonarlint
Then, restart VSCode and run the command SonarQube Inject: Create global config with credentials to servers again and setup servers.
Using this link I created a container and after getting some packages, I want to start a qtcreator 4.0.1 on it. I use a ssh connection to connect to the container. After launching qtcreator I get an error such as this:
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb.
Reinstalling the application may fix this problem.
I installed all prerequisites packages as listed here but still the problem is remained.
I must mention that I am using a privileged container in opposite of the link.
xcb listed as available plug-ins but it does not run. Is there any suggestion to get around this bug?
This answer has the main solution. In my case I find the libqxcb.so in path /path_to_qt/plugins/platforms/ and after running ldd command on it I found that it has not one of its dependency libEGL.so after install this package using sudo apt install libegl-mesa0-dev I could run qtcreator.