jiebi/CodeConvo huggingface dataset:
Instead of 'success dots' in the gutter, all commands seem to think there are fail exit status. Here are my dotfiles: and a branch to help debug: The debug branch just build an array of what commands were that triggered the trap and print them at the start and end of building the prompt. It does show the trap being called twice when shell integration is enabled - and once otherwise. The repro environment/steps: Repros in OSX and WSL Ubuntu 22.04 for me. It uses dotbot. In a scratch user directory you can run ./install to link everything into ~/. Pass to ./install to avoid installing extra tooling it finds missing (pygments/tmux/coreutils)There is a script that get's sourced . This is the root of all evil. It's on the hacky side. The function is small and is (I believe) the only relevant part. I should stop using it, but it's sooooo_ ingrained into my muscle memory. To verify: Removing from makes everything work great with none of the above mentioned problems. One hack, that seems irrelevant is that uses debug trap directly, but also detects and uses the pre-exec infrastructure if it has been loaded (to not break iTerm2's shell integration). I appreciate the time and effort going into this feature. It's becoming a shockingly advanced embedded shell environment.
thanks again, planning on tackling this in June
I use just merged in a fix for this. It would be great if someone could help verify in tomorrow's insiders build as I'm not normally a user of bash-preexec.
Still some problems around . Very simple repro: clean environment. My bash and vscode versions are: use this .bashrc: For me (In WSL, repros in plain OSX): ! Without ! If extdebug works, then this would be the next simplest test (I think). Same clean environment. The following
Are there verif steps for this?
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Currently, it is treated as . (I have disabled all my extensions and confirm this behavior) It does support as comment like does. A simple workaround now is to set But it's nice to have it built in supported.
Clone the repository Open the repository in VS Code Insiders Rename to Open the file: Confirm that the file type is detected as "Ignore" Confirm that the comments in the file are coloured correctly
Type: <bBug</bCC CC I create a terminal in VSCode, press shift+alt+f1 to display the accessibility help, and then press the esc key to dismiss the displayed information. I believe that the focus should be moved back to the terminal but it doesn't. I need to press shift+tab to move the focus back to the terminal. I tested using orca but I believe the same happens using nvda, I'll test later. VS Code version: Code - Insiders 1.76.0-insider (, 2023-02-09T05:23:03.109Z) OS version: Linux x64 6.1.9-200.fc37.x8664 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (37)</summaryExtensionVersion ------ doxdocgen1.4.0 vscode-markdownlint0.49.0 vscode-chatgpt3.5.9 rest-client0.25.1 better-cpp-syntax1.17.2 azure-pipelines1.208.0 vscode-docker1.23.3 csharp1.25.4 vscode-kubernetes-tools1.3.11 remote-containers0.278.0 remote-ssh0.97. remote-ssh-edit0.84.0 azure-account0.11.3 cmake-tools1.13.45 cpptools1.14.1 cpptools-extension-pack1.3.0 makefile-tools0.6.0 powershell-preview2023.2.0 remote-explorer0.3. vsliveshare1.0.5828 fabric8-analytics0.3.6 java1.15. vscode-xml0.25. vscode-yaml1.11.0 sonarlint-vscode3.14.0 cmake0.0.17 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-boot-dev-pack0.2.1 vscode-spring-boot1.44.0 vscode-java-debug0.48.0 vscode-java-dependency0.21. vscode-java-pack0.25. vscode-java-test0.37. vscode-maven0.40.
! It could be that I caused this, but I doubt it (injected text has nothing to do with the gutter, maybe they shared a CSS rule).
I can reproduce but I'm not aware of any changes in that area from the debug side.
I would like to work on this issue!
Before fixing anything we should do a "git bisect" to find the commit that broke this.
commit . it should
thanks for pointing out the commit! If you like, you can provide a PR, that would be awesome!
PR
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: No. Related to extension api <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.79.0-insider OS Version: Macintosh; Intel Mac OS X 1340 Getting a session for a Microsoft account for the default tenant, and also getting a session for the account but for a specific tenant results in two items for the same account appearing in the Accounts menu. <img width="546" alt="image" src=""Steps to Reproduce: First call with the following scopes: . And another call to with these scopes: I want to point out that the account objects on the returned sessions are actually different: <br<details<summaryMicrosoft Authentication provider logs</summary<p</p</detailscc:
These accounts aren't duplicate, they are sessions that exist for each signed-in tenant. I think the best solution would be to change the account label to . This would match what the Azure portal does. <img width="201" alt="image" src=""I think this is an important change to make because this really doesn't look good and is confusing to users. Especially when users are trying to sign out. The screenshot below is after I sign in with a single Microsoft account that has 4 tenants. Having 4 tenants is not uncommon. <img width="515" alt="image" src=""
Yeah this goes back to that "technically they're different accounts because they're in different tenants" thing. I'm inclined to agree with you and dedupe per-label.
Although that would present better, I think deduping on the label wouldn't be great unless you made the label more standard across tenants.
In that case, I think changing the label to be just email would be best. Then all of these sessions in my example screenshot could be grouped as one. If you deduped per-label with the current labelling it would show two accounts, one that represents 3 tenants, and another representing another single tenant. That would still be pretty confusing. IMO there's two options: Dedupe by email and hide all tenant related stuff. Signing out of that account removes all sessions associated with that email, regardless of tenant. Don't dedupe at all, instead include the tenant display name in the label as .
says this works!
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.91.0 (Universal) OS Version: Darwin arm64 23.5.0 Steps to Reproduce: new profile test to new profile in Devcontainer sample container is loaded without extensions. Opening in DevContainer with the default profile works correctly. Works correctly with the previous version of vscode 1.90.2
Same For Me
+1 extensions from are not enabled in the container when using a custom profile. Although the container logs does report that the extension was successfully installed, and I can see it is installed in the container, in . It's just not enabled when using a custom vscode profile.
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.83.0 OS Version: macOS Sonoma(14.0) Steps to Reproduce: the color theme to high contrast any theme to extension search (I have attached a picture below which you will see there) will see no border-right edge of the install button !
I'll start trying to fix this weird border-right
Repro: Open DevTools: !
This started occurring recently due to It is now possible to get this warning from various parts of the product.
Yes. That's on purpose and the goal is to get rid of invalid URIs in our system. So, when your code causes such warnings, you need to change it ;-). I can consult. The background is that an URI must have a scheme but we never enforced that. The warning I have is the first step into that direction.
The warning is valid. We're passing a path to , which is wrong. Git remote addresses are not always uris, they can be paths; even relative paths.
So the consumers of should beforehand check if what they are passing is valid uri or not? Doesnt that fail the purpose of ? is used to parse json content. We can pass non json to it as well. It throws an error. Can we not expect something similar from ? If we are worried that throwing errors will break existing code, then can we have a stricter that we can use?
Yes, parse will throw an error but it never used to do that for missing scheme. I didn't think it's a good idea to now start throwing errors at first because not everyone encloses in a try catch block and also often people confuse and .
The new notifications pop open at the lower right corner of the editor. Some command palette actions pop these up with a button that I need to click on to proceed. In these cases, I have to move my mouse from the top center of the window down to the bottom right corner of the window. One such example is the "Git: Delete branch" command. I have to click on the branch I want to delete from the drop down selector, then click the notification button far away in the corner to confirm the delete. If I am deleting multiple branches at a time (because I'm finally cleaning up my local state ) I have to move the mouse back and forth a ton of times so now I use a terminal for this task instead. It would be nice to have an option that lets me decide where I want the notifications to appear. I would choose the top right corner to reduce mouse movement.
I'll narrow this issue down to make the delete branch popup a modal one, which it should be anyways.
I'm trying to repro, but don't get any such popup after selecting a branch to delete. The branch is instantly deleted. I'm on Mac OS X 10.11.16, vscode version 1.21.1
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --I work on an extension that has a custom tree view. Some of the items don't have meaningful extra information to show in a tooltip but setting the field in the to or results in the label being used for the tooltip which looks odd as it provides no additional information. We would like it if there was some way to disable tooltips for a tree item. It might be hard to used for that now as that would be a breaking change but perhaps there is some other approach that would be possible. I would note that if the tooltip is required for accessibility in some way then I'm happy that it stays but I think that angle is covered by the aria-label attribute and the tooltip is something else entirely. I have searched and I can't see reference to this from an extension API point of view in the current issues. I am not well versed in the VS Code code base but I believe the issue comes from these lines:
Here is an example screenshot of the issue: ! The supported features are programmatically detected and we don't have a reliable way of providing any additional useful information for the tooltip so being able to avoid it entirely would be desirable.
I think that allowing extensions to have no tooltip is a good feature request. Form an API perspective, do you think setting to empty string is an ok way to accomplish this? I don't think we should use since that would be a big disruption to the current behavior (where the is used).
Yeah, that makes sense to me.
To verify, modify an extension that provides a tree view so that the of it's tree items is an empty string. Verify that no hover is shown on those tree items. You can use the sample for this:
contribute command that uses enablement assign a keybinding, via :bug: enablement isn't honoured
When users configure keybindings we allow them to change preconditions as well, e.g rename requires an editable document so I don't plan to have a different strategy for contributed commands
I don't see the nice "Command 'Hello World' is not enabled in the current context." info toast when I try the keybinding though. I only see that message when I try to run it from the command palette. The command correctly doesn't run when not enabled though.
Yeah, that's the design. Keybindings don't show messages
Type: <bBug</bstep 1 - Run any command or project whose lines does'nt fit in single line step 2 - Your terminal can be full sized or small size does'nt matter step 3- Presss Alt + z to wrap line in terminal Step 4 - Resize your terminal window Example - If initially terminal window height is 100px from the bottom then word wrap using Alt + z and after that increase or discrease the size of terminal window. You will find that content is still showing in 100px of height VS Code version: Code 1.91.0 (, 2024-07-01T18:52:41.959Z) OS version: Linux x64 5.15.0-113-generic Modes: <!-- generated by issue reporter --
!
Thanks for fixing the issue One more questions Is there any way to off wrap word in terminal parmanent. I have to use Alt + z each time when I run my project
there is not
Can you make it happen like Eclipse Please
i haven't seen it in eclipse but I'm guessing they're using the old console api on windows which isn't really compatible with the pty based system that we use.
Works, but I never see a horizontal scrollbar with word wrap disabled, should I expect to? I see it in the screenshot above.
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.47.2 (user setup) OS Version: Windows_NT x64 10.0. Steps to Reproduce: a file named in any directory. the file with VS Code. file is opened with the "JSON" language mode (instead of the expected "JSON with Comments" mode). Other file names, e.g. , are also opened in "JSON" language mode. In contrast, is opened in "JSON with Comments" mode even if the file name contains suffixes, e.g. . <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
This is easily fixable, look at the relevant code: Submit a PR
Thank you. Is a local build/test warranted, or would a direct PR suffice? Asking because I don't have a local build environment right now (and setting up one would take some time)
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --VS Code currently associates the extension with the Make language. is another common file extension for files included by s. It's associated with Make by , i.e. files are recognized by , and there are a few dozen public . VS Code should recognize this extension automatically.
could you point me to some documentation about please?
Hi I've updated the issue description with some additional information. Notably, , which I consider to be a fairly canonical source. I've not any of the other file extensions recognized by GitHub Linguist for Make, as I've not seen them in use. Anecdotally, my employer has been using the extension internally since at least 2001.
Here are some additional examples which demonstrate inclusion of files by s:
That's good enough for me, thank you!
/verified
Type: <bBug</bipynb notebook bug In dev tools, see: VS Code version: Code - Insiders 1.70.0-insider (Universal) (, 2022-07-26T05:17:37.262Z) OS version: Darwin x64 21.5.0 Modes: <details<summarySystem Info</summary </details<!-- generated by issue reporter --
Looks like the directory is excluded from publish: You likely want to have the notebook code go to a different directory, such as instead of the dir
Just changed that inside esbuild, didn't realize that out wasn't included. I had been having an issue with needing to run while using OSS, could that be related? I'll make a PR to adjust and
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.70.0 (Universal) OS Version: Darwin x64 19.6.0 Steps to Reproduce: to delete a file with nested files When you right click and hit "delete", vscode does nothing and the file and its nested files remain. You must open the parent and delete each nested file and then you are able to delete the parent file.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Also, I think it would be a good idea for an option to rename all nested files when the parent is renamed.
based on the setting description for file nesting, I expected a file I created in a folder to be nested under the that is in that same folder. Is that the wrong expectation here?
That is correct. I'm seeing that here <img width="457" alt="image" src="https://user-"
From : Error: TreeError [FileExplorer] Data tree node not found: ExplorerItem:
Any idea here because there's no explorer stack involved this might be a tree issue
You can try this. Enable fileNesting and select a file with nesting, control+c, the error would appear. The chosen file should be in preview.
third line in the stack frame:
This also happens when you try to open a file with enter or space keys. ! Pressing delete instead of enter will display the same error. (related issue: ) Once the nested files are expanded, this error does not occur until the next window reload, perhaps because the node is to the tree.
Thanks for the repro
! Testing
I'll try to deal with this
I'm sorry, I would like to ask a simple question. If I want to use this accessibility mode, do I need a software like NVDA to make it work? Or if I only have VS Code, can I still trigger this functionality?
Hey you can enable this with the command - a status bar indicator will appear
I used to be able to trigger , but now when I trigger it, it will show up in the lower left corner, but it won't have any function, which is a bit strange, are and the same function, I didn't find
Yes that's what I had meant. Hm, maybe a recent regression? Last time I tried this, it worked for me. I'll investigate tomorrow
Also, re the question of do you need to use a screen reader, it depends on what you're trying to do/ test. With that mode on, certain audio cues will (should) be enabled by default for example.
I have used this function once before, and it is true that the audio will play after it is turned on, but this time there is no response, I will check again to see if it is a problem with my settings
you can test this - and it's working for me with: screen reader mode status bar item appears in the terminal hear sound screen reader mode status bar item disappears no sound
Thanks! This work for me
I started trying to solve the problem
Description Currently, when editing a file, the command <kbdctrl</kbd+<kbdshift</kbd+<kbda</kbd(toggle block comment) generates the following comment placeholder . I wonder if it might be also wise to include this as an auto-closing pair so that when users attempt to write the closing is automatically like other languages (ex: Typescript).
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the for VS Code. See also our guidelines. Happy Coding!
I'm not quite sure as to who or where the owner is for the extension. Looking at the I noticed multiple past updates to support additional features. Isn't the proposed feature request present in the issue similar to those past updates?
Oh, you are right. This part is us, not the extension. Sorry for the confusion...
Looks like a good change to me. Feel free to make a pull request.
Not able to reproduce ctrl+shift+a not having any effect.
I assume you are editing a file, but sorry the keybinding I mentioned is for Linux, on macOS for example the keybinding is . The easiest way to test is to simply run the command from the menu 🡒 :)
Got it, in windows it is Shift+Alt+A.
I forgot to mention I won't be able to submit a PR myself due to my company policy. If anyone would like to take on the issue, please feel free to do so :)
In that case, I am more than happy to make a pull request for this. Thanks for the information. I will submit one soon.
thank you!