After upgrading Docker/Docker-Desktop to 4.0.0
i'm not able to start Visual Studio Code over Docker-Desktop.
Docker Desktop show an error: Error invoking remote method 'desktop-go-backend': Error: Internal Server Error
and if i start Visual Studio Code not over Docker Desktop, Visual Studio Code can not connect to WSL.
Console Output come with an error like this:
/home/xxxx/.vscode-server/bin/xxxxxxxxxxxxxxxxxxxxxxxxxx/bin/code: not found
After searching in outer issues with VS Code and WSL, i found the solution for me:
I delete the directory: /home/xxxxx/.vscode-server/ in the WSL/Distribution
because the directory /home/xxxxx/.vscode-server/bin/xxxxxxxxxxxxxxxxxxxxxxxxxx/ was empty
After deleting the directory and restart VS Code the needed files are reinstalled and all working like before.
I had an issue with a similar message:
Error invoking remote method 'desktop-go-backend': [object Object]
I managed to fix this by removing the spaces in my source code folder.
Related
I've followed this tutorial to setting up Zerobrane IDE for debugging openresty:
http://notebook.kulchenko.com/zerobrane/debugging-openresty-nginx-lua-scripts-with-zerobrane-studio.
I installed openresty 1.19.3.1 from a brew formula, and lua scripts are working.
Double checked everything with zerobrane, the error i got:
Debugger server started at vgh.local:8172.
Can't start debugging for '/usr/local/Cellar/openresty/1.19.3.1_1/nginx/lua/content.lua'. Compilation error:
Debugger connection closed
Debugging session completed (traced 0 instructions).
Refused a request to start a new debugging session as there is one in progress already.
What should i check?
This is the conf i have on macos, but i got the same error on a linux (ubuntu 20.10):
lua_package_path '/Applications/ZeroBraneStudio.app/Contents/ZeroBraneStudio/lualibs/?/?.lua;/Applications/ZeroBraneStudio.app/Contents/ZeroBraneStudio/lualibs/?.lua;;';
lua_package_cpath '/Applications/ZeroBraneStudio.app/Contents/ZeroBraneStudio/bin/clibs/?.dylib;;';
You don't say what version of ZeroBrane Studio you are using, but you'll need to use the latest one from the master branch in the repository, as there have been several openresty-related fixes applied to the debugger and merged recently .
So I was able to create an addon using the Selenium drivers and packages. However, even after successful loading of the addon in the Studio, when I try to run my command, I am getting an error mentioning that the command was not found.
Here's the error Image:
The command is clearly showing in the addon information window, however when I try running it I'm getting this error.
When you write the name of your command in visual studio, try to write it in small letters.
Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
I tried to install ejabberd 2.1.11 for windows on my Windows system, but at the final stage of installation it given post installation error. Couple of some of the last lines in the intallation logs says:
***Executing final installation script
Error executing post installation script
C:\Program Files (x86)\ejabberd-2.1.11\bin\postinstall.cmd
./ejabberdctl: erl.exe: can't execute: (14001) Error 14001
Creating Uninstalle***r
Though the shortcuts are created on the system but trying to start the server gives following error
./ejabberdctl: erl.exe: can't execute: (14001) Error 14001
The VC++ 2008 is already installed on the system. While searching I found the following post on stackoverflow:
How to install ejabberd community version on Windows XP?
But this too did not help. Has anyone else encountered the same scenario? Your suggestion would be greatly appreciated.
when i run Msbuild web.csproj i get the following error:
AfterBuild target> -> C:..\web\obj\debug\csautoparameterize\original\web.config
: error ASPconfig: an error occurred
loading a configuration file:
Directory C:..\web\obj\debug\csautoparameterize\original\Configs'
does not exist. Fail to start
monitoring file changes.
if i open visual studio (2010)..clean solution and rebuild, its fine. if i try to do publish via visual studio, this error returns and i cant build again (until i clean solution).
any ideas?
thanks
Is that a network drive? I was getting a similar error when I had my SVN working copy on a network drive, apparently the folder monitoring service for the test server completely freaks out when it's not a physical drive.