this is the project home
https://github.com/neovim/neovim
i'm try to use cmake to build it,but failed .
Do you have any success,tell me the detail way.
thank you!
At the moment the master branch of Neovim does not build in Windows.
There is an issue for Windows support#1749 with an open pull request#810. However the terminal support in that branch is currently broken.
In that first link you can find some instructions on how to build, and a list of issues that still need fixing for Windows support.
Related
Today I tried to use the copilot, but suddenly this error start appearing:
[INFO] [fetch] [2022-05-19T21:00:55.452Z] Please upgrade your Copilot extension to continue using this service.
I tried to uninstall and install again and reload, but nothing happens, anyone have any idea how to solve this problem?
There's an error description in the image below:
This can be resolved by upgrading VSCode itself: Help → Check for Updates / Install Available Updates.
You may or may not need to re-install the extension and re-authenticate with git.
Reference: https://github.com/github/feedback/discussions/15684
In my case (on a mac) I had to do the following:
Move Visual Studio Code from Downloads to Applications
Restart
Update Visual Studio Code
Sign into Github
Open extensions and locate Github CoPilot
Click "Reload Required"
As #emragins suggested, go to Help and check for updates/restart to update
Once you are back on VS Code check if the Co-pilot is activated.
If it is not activated/still gives the same error.
Search for co-pilot in VS Code extensions search
Click on co-pilot extension in the search results, you should see restart/reload required.
Reload and it should be working now. If not try closing VS Code and opening it now.
You should uninstall the extension and download the latest version from this page in the form of VSIX file. After that you can install the extension from that VSIX file.
I think it is because there is some API changes and the latest version of the extension. However, it is still marked as preview. When we click on install from the built-in extension browser, it just install the latest stable version.
https://marketplace.visualstudio.com/items?itemName=GitHub.copilot
if you are on a linux device, update your vscode first then update your co pilot extension it will work.
I've installed the Playwright vscode extension but when I go to the testing area I get a "No tests have been found in this workspace" message. But when I run $> playwright test on the CLI it works like a charm. The weird thing is, that some time ago it was perfectly working in VSCode.
When I click the reload icon I get
But then after a couple of seconds I get back where I started.
When I click the blue button I go to the list of extension
I'm not very sure what I am suppose to install here. Also, it did work in the past already.
This is the extension I installed for Playwright:
Any suggestion what is going on here in my VSCode?
I had the same issue, the only thing that helps me is VS code update, this extension works only on the latest version on VS code.
tests section
I had the Microsoft extension installed and latest VSCode and got the same message in the Testing panel after using the "Install Playwright" command.
For me it was restarting VSCode completely that made the extension work. Note this was a full app restart and not just the "Developer: Reload Window" command.
Update Node on your system to the latest and it will resolve it. I had the same issue and by updating node, Vs Code immidiately detected all the test files and it works like a charm.
Check that you're using a supported version of playwright.
In the "details" section, the extention I have installed says
This extension works with Playwright Test version v1.19+ or newer.
I was using Playwright version 1.17, and faced this same issue. Updating to use version 1.19 fixed it.
I had the same issue with Playwright version 1.26.0
I actually had a github issue open
https://github.com/microsoft/playwright/issues/17687
Updating to Playwright version 1.26.1 solved the problem and tests were found once again.
I've had the same issue with a vs code which has been installed on a ubuntu box using the "ubuntu software" installer. This only installs snaps, which probably caused the issue. First I uninstalled the snap and deleted the .vscode folder in the users home directory.
After using apt for installation ( as explained here https://linuxize.com/post/how-to-install-visual-studio-code-on-ubuntu-20-04/ ), the playwright plugin worked without any issues.
Please update your Playwright version (Version 1.28.1 at the time of this post) to the latest, (Steps below),
First Check your current version
npx #playwright/test --version
Update to the latest version
npm install #playwright/test#latest
Install Browsers
npx playwright install
Check the updated version
npx #playwright/test --version
And also install/update the latest version of the Playwright Test for VSCode (v1.0.1 at the time of this post) and reload the IDE.
This can be done by simply as follows,
Go to Extensions
Search for "Playwright Test for VSCode"
Update or install the given latest version
It Worked for me.
I had the same issue when trying to use existing tests and the latest available version of VSCode and NodeJS just installed on my PC. It that the issue is in the lock files (yarn.lock and parameters-lock.json) contained conflicting requirements, I left only those files that already were with the tests and everything immediately worked after clicking the "update tests" button.
I've been at this for a couple of days and I can't figure this out.
When I run git status on my terminal, it's giving me a different result than what my visual studio 2022 shows me. I think this all started when i added git lfs to my repo using brew so it doesnt track the larger files i have.
For example, in my terminal, it's showing: . Usually they show the same files always and never have an issue.
but then on the same branch in visual studio 2022, it's showing, it's showing this:
so far, I've tried:
Restarting my computer and visual studio(I had to try)
Using the sync button (next to the pushbutton) in visual studio.
Running git remote update on my terminal
I can't find anything else on SO to try.
Any and all help or direction is appreciated!
Check your .gitattributes files; since you added git lfs, it tracks the large file extensions with the .gitattributes file. That may be the reason why Visual Studio is not tracking those files, but your git terminal does.
There is a bug which i also face in visual studio.
Sometimes the VSCode cannot track the files which are updated.
what you can try is update the visual studio to see if the bug is fixed or not.
Mine was resolved by updating the VS.
PS: try using GitLens for a broader view of git.
I have been using copilot for a while now, and one fine day on opening VSCode this error appeared.
"[ERROR] [default] [2022-04-09T08:38:10.995Z] GitHub Copilot could not connect to server. Extension activation failed: "certificate has expired"
I looked up for it everywhere and found nothing, it'd be a great help if someone could fix this for me!
[here's the error and how the extension looks like on the status bar]
Three common causes:
An out of date IDE. Solution: make sure your IDE is up to date
If you're not properly signed in to GitHub CoPilot. Solution: make sure you're signed in to GitHub CoPilot
E.g. In VSCode look on the bottom left, if you see this, you might not be signed in:
Click the icon, and follow the prompts to sign in, then CoPilot should work.
Try closing and reopening your IDE (e.g. vscode), that may also help.
I know its a bit late. But I encountered this problem today. If disabling and restarting doesn't help, you could try:
At uninstall, select Install another version, and select the version before the latest
Reload vscode
After doing this, my copilot started working again.
Two things you should check:
1=> Update VSCode to the latest version
2=> Update GitHub Copilot latest version
From the Menubar, go to View -> Output;
Choose GitHub Copilot from the pulldown on the left to see the log of what is going on in the background.
Go to your Github account and check if you have paid the bill, In my case that was the problem.
In Visual Studio, if you are the one that disabled the Copilot before you can enable the following way.
Either search for "Copilot".
Or go to Tools>>Options>>GitHub>>Copilot
Go to Enable Globally and change from false to True.
Given that GitHub Copilot is so fresh and well-liked, updates are made often. When encountering this kind of problem, I would advise entirely purging and reinstalling.
Installation of GitHub Copilot in Visual Studio Code
The documentation lists extensions for Visual Studio Code, Visual Studio, Neovim, and the JetBrains suite as IDEs that GitHub Copilot supports.
The installation consists of three main steps:
Create a GitHub account (if you don’t have one already).
Go to GitHub Copilot and click on “Start my free trial”. Follow the sign-up steps and make sure to cancel before your 60-day free trial is up (if you don’t want to continue using the tool).
Install the VSCode extension by searching for “GitHub Copilot” on the extensions tab. You’ll be asked to sign in to GitHub, authorize the extension, and then Copilot will be set up.
If you would like a more thorough explanation, my colleague Rafael wrote a great article based on his time with Copilot and VSCode: https://www.scalablepath.com/full-stack/ai-pair-programming-github-copilot-review
I'm looking to migrate my Django project from PyCharm to VsCode, it has source control with github and I'm on a mac. I've looked around, however, I've not come across a step by step guide. Any help would be greatly appreciated.
I don't think there should be any problem as this is just a shift from an IDE to a text editor.
Pycharm maybe creating virtual env automatically for you which now you need to do manually but if you didnot changed anything, the virtual env will also be there.
For github, use git shell or cmd to make changes.
Rest is just codinggg