I have a problem with adding an atmosphere package (std:accounts-ui) to my Meteor application.
Upon running this command:
> meteor add std:accounts-ui
It downloads successfully but gets stuck on Extracting std:accounts-ui#1.2.100...
Eg:
I have left it over night and it's still stuck.
This issue has been reported on GitHub and should hopefully be fixed in a future release.
The problem is that the unzip software doesn't get configured properly. This can be solved by uninstalling all unzip software and then running your Meteor application which will reinstall appropriate unzip software correctly configured.
Related
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
Could anyone please help me with steps to upgrade "My WebMethods Server" from 10.1 to 10.5 using/applying patches/fixes?
Upgrade document is clear enaough if you read it all but just in case you want to play safe, this is how I’ve done it:
1- Install DBConfigurator to new location (If you are performing upgrade on the same machine).
2- Install Update Manager.
3- Install latest fixes for DBConfguratior.
4- Run the latest db scripts. (If you installed the scripts already, perform migrate operation after installing fixes for DBConfguratior).
5- Perform Installation of the new version.
6- Shutdown both old and new instances. Run the migrate utility from the new installation.
7- Migration utility will ask for old version installation directory. (Or you can have an export of the old version as a zip file).
8- Follow the steps guided by migration utility, It will ask couple of questions which you can answer by typing Y or N.
9- If everything goes OK, you should be getting the message below. (Might be different for newer versions.)
Failed migrations
None
Migration successful. Exiting the migration utility.
*** End Integration Server Migration ***
10- Validate the scripts you are using for startup have the new installation directory. I faced a couple of problems with that.
Bonus : Make sure the extendend setting about java compiler have the right path for the jvm. watt.server.compile=…\jvm\jvm\bin\javac -classpath {0} -d {1} {2}
I am trying to build Brave Browser in Windows 10 64bit 15.8GB RAM and more than 200gb in free space.
I am following this repo: https://github.com/brave/brave-browser/wiki
I have installed all the requeriments for the build on Windows, however, when I run npm run init I get the following error:
Downloading CIPD client for windows-amd64 from https://chrome-infra-packages.appspot.com/client?platform=windows-amd64&version=git_revision:db7a486094873e3944b8e27ab5b23a3ae3c401e7...
error: The following untracked working tree files would be overwritten by checkout:
pylint.bat
Please move or remove them before you switch branches.
Aborting
fatal: Could not detach HEAD
Failed to update depot_tools.
Anyone knows why that might be happening? I have tried installing python and setting the enviroment variable, rebooting the machine, tried installing VS Code a few times thinking it might be it but the error is always the same. I have also tried the Brave Community and I cannot see anything similar.
Any help would be appreciated,
I believe it's an upstream problem in Chromium, so a fix should appear in Brave soon. See https://bugs.chromium.org/p/chromium/issues/detail?id=996359 for details, including a potential workaround (though I haven't personally tested it).
An update was downloaded automatically by my 2.6.3.RELEASE Build 201411281425.
STS (Spring Tool Suite) asks to install it and when I click on the pop-up window it does some things and then stops with the following message which seem to indicate that it wants to delete itself.
I can understand why this fails but I am not sure why STS would think that this was possible.
I could not find any instructions about manually installing the zip file that is available as a download as an alternative way to upgrade my installation.
How do I fix the automatic install or manually install the zip?
(I am on Windows 7)
Error message:
An error occurred while uninstalling
session context was:
(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall,
operand=[R]org.springsource.sts.ide.executable.win32.win32.x86_64
3.6.3.201411281415-RELEASE-e44
--> null,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file C:\RAMDrive\spring\STS.exe failed.
File that was copied to backup could not be deleted: C:\RAMDrive\spring\STS.exe
Start the STS you want to upgrade and before you click on "Check for Upgrades", with STS still running, rename the STS.exe file you just started, to something else, like "STS_old.exe". That should do it.
The message sounds strange, I've never seen this before. To install a fresh copy of STS, just download the ZIP file from the download page (the one that matches your operating system and pick the right 32bit or 64bit one, depending on your OS and the JDK you are using). Then unzip, and start STS.exe. That's it.
So I'm trying to make the switch from Bootstrap to Foundation , and I'm attempting to follow the instructions on this page (as I'm trying to install Foundation with Sass), but the instructions on the site are rather unclear to me - I've installed Git, Ruby and NodeJS but every time I get to the step
foundation new MY_PROJECT
I keep getting the error "Can't find Git, you can install it from http://git-scm.com/downloads except I've already installed it (and reinstalled it, twice actually) and I have no idea what to do to fix it. Perhaps someone could lay out the instructions from start to finish in more concrete terms so that I can understand?
Strangely enough, I reinstalled Git and found that you have to adjust Git's PATH option so that it runs Git from the Command Prompt (essentially, pick the second option on the "Adjusting your PATH environment" screen when installing Git).
Not entirely sure why I didn't realize that before, but it fixed the problem for me!
It is probably some kind of path issue.
You could also run Git Bash that was installed when you installed Git and then execute the foundation new MY_PROJECT command from there. It worked for me :)