jiebi/CodeConvo huggingface dataset:
My extension is this one: Find attached a sample project: These are the steps: Install the extension Unzip in its own folder Open the folder with VSCode With selected, issue the command Toggle Design/Code This will open up the webview, and with the changes, you could see in the console the issues Find here a video with the steps on how to open the webview, and the behavior when its working: ! Thanks!
Needless to say that if I should perform any changes on the extension to make it work, it's not a problem at all. That is, if I can get an idea on what the changes are, have no problem on that. :-) Thanks!
Thanks for the repo steps I have a potential Please try the next VS Code insiders build that comes out and let me know if you still see the problem. With the fix, things seem to be loading correctly: <img width="1129" alt="Screenshot 2023-04-12 at 4 06 24 PM" src="https://user-"
Checked insiders, but not sure if the fix got through, as I see some checks failed: ! Also tried update from the repository, and it seems still is not merged. In any case, what I see in your shot is that the Tool Palette is missing content. The content is provided by loading an external file called "" and it seems the webview is not able to load it: ! Will keep checking, THANKS!
ignore my last message, I have merged your changes locally and works perfect! So once this is merged, consider the issue fixed, thanks a lot!! !
<!-- 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!
/verified
creates a tree view opens the tree view disposes the tree view while it's still open creates the tree view again The tree view will stay empty until it's is toggled Real world repo (also works as steps to verify): to a Codespace (to use a specific build of VS Code you can specify a commit in the URL with , ex ) the Remote Explorer the page. This will cause the Codespace to load with the remote explorer visible 'll see that the Codespace view in the remote explorer is empty
update
<img width="1792" alt="image" src="https://user-"Hi, like visible on the screenshot, more than half of the terminal width in vertical mode is taken to display the path of the file where the log originated. I think this is not relevant to many of us since the path will point to the logger file At some point it gets really hard to read the logs Just to have an option to display path in cli would be enought for me. My screen resolution is 3072x1920 and my zoom level is -0.5 (at 0 it is even worst)
This has always been a bit off- I think only showing the file name would be sufficient
To be honest, who even needs the filename? When debugging I know what my messages mean and where they are generated. If I don't, a simple clickable elipsis will save space and perform the same function by bringing me directly to the line of code.
Type: <bBug</bSteps to reproduce: a fresh, vanilla VS Code Insiders installation without any extensions. and open a new folder. , open it, and save it with the following contents: Actual results: A warning is reported in Problems tab and via yellow squiggles at line 10, column 25 (= character of the line specifying the ): Expected results: No warning is reported. Additional information: The problem matcher has been copied directly from the (). VS Code should not display warnings for unmodified examples from the docs. This also occurs in the current non-insiders release 1.74.0. VS Code version: Code - Insiders 1.75.0-insider (, 2022-12-08T05:20:51.149Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I can repro this. probably caused by your changes to the schema - could you pls take a look?
Of course. I'll submit the fix.
The PR is ready for review.
<!-- 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!
/verified Thanks for the quick fix!
I see that settings sync is suspended because of invalid token and token is not getting refreshed / updated. Sync LogMicrosoft Account Log Did not work even after Reloading the window / opening new window. Restarting VS Code worked. any insights? Is there a cache on the extension?
From the account log, the token gets refreshed before it expires. This should trigger an event which causes the new token to get set, but it seems like something about this is failing, since we then get into a loop of getting a 401 and trying to resolve the access token.
Every time we see a failure, we unset the token and send token failed request and we update the token by getting it from the account sessions. Looks like we are getting an invalid token from the account sessions. Can you please check if that can happen?
Found the issue! The token was not being set in the shared process
Easier steps to verify: in with an account to preferences sync out of the same account in to the account again Preferences sync should restart without any error.
image in Luna paint, save. on entry in SCM viewlet to see diff some more a drink to resize the window diff editor loads Haven't tried in other custom editors, don't know if this is an issue with custom editor openers or in Luna.
Seems like a core issue, also happens with hex editor with:
This seems like an important regression. No idea what changed in custom editor land
This seems to have been caused by /cc The current calls causes the webviews to end up with height in this case. On the first call to never gets invoked. Previously it got invoked before the webview was even created Looking to see what that proper fix would be for this. Some potential ideas: I feel like should probably always be invoked at least once on a newly created editorI'm not sure why the passed in always has zero height but that seems wrong. If that element has , then I believe the code would work The issue seems to be that and both have zero height
I get the following error with these steps, unfortunately... So I could not repro this. ! I am pretty sure the grid calls layout to its views whenver their sizes change. Is it possible that some layer between the grid and your webview is caching something and not calling on you? Namely the editor group layer. For example, I see a potential problem here: If the layout comes, and is , the dimension will be lost forever, since the grid will no longer send repeated layout calls when dimensions don't change. The instance should remember the last and pass it along to the active editor pane, as soon as it comes along. cc A very similar situation happened here:
I hit the same exception when following hex editor alternative steps. This might be a new bug?
Maybe is the same and has easy steps to reproduce.
Thanks the lack of milestone was hiding that issue from me! Will check it out.
btw the is storing the dimensions and applies them here already when making the control visible:
That exception you see I receive in the official build of insiders, but not when running out of sources. It implies that the resource URI is undefined which shouldn't be possible. If you have any ideas or would like to help me discover what is causing this let me know
For the hex editor, I had trouble reproducing this until I set .
<!-- 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.68.1 OS Version: Windows 10 Steps to Reproduce: a Markdown file and open "Open Preview to the Side" add line: ! image in preview second line: ! second image shows up. Remove the line above image preview shows 2 images and does not update properly !
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.68.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Still happens in 1.68.1. Updating bug
Does this reproduce in the with all ?
Yes still happens with all extensions disabled
<!-- 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.67.2 OS Version: MacOS Monterey 12.4 (default zsh terminal) Steps to Reproduce: a folder containing an "Umlaut" (äöü) folder in VSCode and launch/use a terminal (for testing I used echo something in zsh) VSCode restarting, VSCode fails to restore previous session as "the directory doesn't exist" However, if there is no "Umlaut" included in the path somewhere, this problem won't occur. This issue should affect at least all german VSCode-Users (like me) who want to open a folder on their Mac located in OneDrive. The problem is that the filepath for such files looks like "~/Library/CloudStorage/OneDrive-Persönlich/..." and restoring a session isn't possible for any folder/file in OneDrive, which is a little bit inconvenient. There might also just be a problem with my terminals encoding (currently set to UTF-8 so should work I guess) that it can't open the working directory with how it spells (in this case) the ö in the filepath: <img width="390" alt="Bildschirmfoto 2022-05-23 um 00 04 17" src="https://user-"(when I try to cd to that filepath it doesn't recognize the oxccx88 as ö and says the path doesn't exist) Thanks for help in advantage :) Greetings, Fussel
Related:
Is this a windows issue only? I can't replicate this issue. I'm running Arch Linux.
the OP reported on macOS which shares most code with Linux
I'm trying to replicate the issue because I want to see if I can contribute to fixing it, but I can't seem to replicate it. I have a folder named "äöü" and I open the integrated terminal and run "echo hey". I close VSCode and reopen it, but it restores the session like it's supposed to. I even tried running a task that runs "echo hey" and it does the same.
do you close all VS Code windows and reopen? Just closing one of many will keep the original process running and reconnect to it.
I am trying to trace this bug. But it is kind of tricky because it is NOT reproducable on OSS dev build. It is reproducable on stable or latest insider production release though. On production release, after running a command in the terminal, somehow Unicode characters in the current path was saved incorrectly. (You can also see an incorrect terminal title updated.) On OSS dev build, Unicode characters in the path seems saving correctly and there is no issue restoring or splitting the terminal.
that's odd, could it be one of your settings?
I have zero settings for insider and OSS dev version. I only have some settings for the stable version. My system environment is same as OP's.
Attached a video to show the issue. https://user-
I wonder why this isn't happening in OSS: ! I think you must have settings in Insiders there because the default value is just ? Unless that's the same format zsh outputs its title?
No. I don't have any settings for insider. ! The final tab title is affected by other settings such as or ! After some testing, I can confirm that isn't updated into title sometimes. It might be another bug there but it is off-topic.
It seems like event fired unexpectedly with wrong path.
I also tried to reproduce the problem on Ubuntu but I wasn't successful (both the original problem and the split-terminal one). I even tried Persian and Arabic special letters but still had no chance.
To verifier: When testing make sure shell integration is off
a directory at path: /Users/ma//demoproject.(contains Chinese component) the directory from VSCode top menu: File - Open... a new terminal from top menu: Terminal - New Terminal. and terminal window automatically goes to path (demoproject). Command + Q shortcut to quit VSCode completely. VSCode from mac dock icon. and VSCode shows error: The terminal process failed to launch: Starting directory (cwd) "/Users/ma/xe6x9cxacxe5x9cxb0/demoproject" does not exist. the path in step1 does not contain Chinese(like /Users/ma/local/demoproject.), no error shows. the error only shows when the path contains Chinese. Extra VSCode information Version: 1.65.2 (Universal) Commit: Date: 2022-03-10T14:33:49.188Z (1 wk ago) Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 21.4.0
To verifier: When testing make sure shell integration is off
when split terminal in chinese path,error!
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.609 --- <!-- score: 0.558 --- <!-- score: 0.557 --- <!-- score: 0.499 --- <!-- score: 0.499 --<!-- potentialduplicatescomment --
I think this is language's problem.English path is very well.
It looks like your report is missing some important information, See for more info on how to report actionable terminal issues.
Thanks for your reply! version: 1.39.2 submit: Data Time: 2019-10-15T15:33:00.827Z Electron: 4.2.10 Chrome: 69.0.3497.128 10.11.0 V8: 6.9.427.31-electron.0 OS: Darwin x64 19.0.0 !
Thanks, you can probably workaround this with this setting:
I has try this settings by your suggestion. And it really not error.Thanks!But this way to create a terminal is not my default way.When I create a new terminal.It go to its father's file path , not it is before. If has a way to realize my need? !
Yeah that's what the setting does, you can't get what you're after until we fix this bug.
OK!I understand.Thank you!
I guess this is obvious, but the problem also occurs with European characters (at least french), and very likely with Arabic, Japanese, Indian, Korean characters as well. I also switched to in order to work around the problem.
I had this issue with the project folder itself containing unicode (greek letters). To my surprise, the hack still worked, the new terminal now sucesfully launches in the project folder.
Also happens when the cwd is set via runInTerminal
Note that in the latter case, it's not just the cwd that's affected - it's also all the command line arguments.
good point, this is probably an issue in debug land actually or related to encoding in the shell. Reopening it.
To verifier: When testing make sure shell integration is off
in vscode , the formula is rendered with katex, an KaTeX parse Error occurred ! in pycharm , it's rendered properly with mathjax ! latex code:
The equation renders fine if you wrap it in so I reckon it's related to how we handle bare math blocks. Relevant code:
wow
Hi Can I work on this?
sure
Can you let me know where to get started? As per the last comment, it works when wrapping with "$$" so I figure I need to look into how vscode is rendering lateX in general? any other pointers?
the reason is probably katex can't process environments outside $$ , but i wonder if katex has a similar option 'processEnvironments' like MathJax provides
This is the same for .NET Interactive
This is indeed a pain - especially for someone still going through the learning process and not a LaTeX expert by any means.
They used to finish in 3m24s before - […]-5f82-0dbc-&t=-371d-5daa-d7a2-
I can confirm that tests started timing out after this commit - The first commit that is started happening is Checking what commits in between would have caused it. FYI
Assigning to as one of his commits has caused this timeout.
Mac seems to be passing pretty reliably now but now windows fails consistently on two tests Been adding a bunch of logging to investigate this. Here's the relevant new error: The service worker should be intercepting this request so it should never be going to the network at all here. Taking a look to see if I can figure out what is going on
Actually it's not windows specific: its Firefox specific. The windows browser tests just happen to be the only ones using Firefox Can reproduce on Mac too
For example: Context:
As we anticipate we might need shell scoping as well in the future, use something similar to instead. Updated proposal: One issue with this is that carries optional properties. Hence an alternative could be:
The required would need to be removed when we a second one anyway, we can just treat and the same as
Sorry what do you mean by the "second one"? Mostly I was trying to follow : But I guess we don't have to strictly follow it?
by a second one I mean a second scope, we don't want the user to explicitly enumerate all the scopes to set it which would do.
Updated proposal:
Closing in favor of as these issues were only open to finalize proposed API.
Moving this out of June as it's a feature request.
I was expecting this so it's easier to understand for an API user:
That's what I had initially had , you're the one who recommended that perhaps we should put it inside itself:
API sync also seemed to be in agreement with that, but maybe we should check again.
my mistake, I forgot some of the conversations as this has gone through a few iterations
Based on discussion in API sync, we should probably deprecate existing API and merge it with the scoped one (similar to )
Assigning myself too so it's easier for me to track
When viewing contributions, is it possible to open the preview of the markdown directly instead of the file? ! as opposed to ! I can open preview using: !
since this is an advanced feature I think the raw markdown is more flexible as the user can navigate and copy section of it better. So I don't think this is a necessary change personally
Feedback before finalization: Add an interface implements Add to the Clarify how scoped interacts with the non-scoped collection Don't deprecate
Should we also call out how it's applied in addition to (and after) the global collection? Looks good otherwise
Sure, I have modified the docstrings to append it I plan to have the implementation ready but only merge and adopt it in Python extension next week to avoid multiple iterations.
<!-- 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.80.0 OS Version: macOS Steps to Reproduce: vscode itself assigned this css var to but monaco-editor doesn't have this, it only has so should be , too.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.80.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Issue Type: <bBug</bSemantic token colorization fails when a token type ID matching any object.prototype property name is provided. Some examples are: , and . is the most problematic name since it is likely to be used as a token type ID. Any string should be able to be used as a token type ID without causing the colorization to fail. Because tries to call on what was thought to be a but was actually a , which throws a TypeError and causes the colorization to fail. The easiest way is probably to use a instead of an object for . Another solution might be to instantiate using instead of an object literal in order to avoid the object.prototype. VS Code version: Code 1.47.2 (, 2020-07-15T18:22:15.161Z) OS version: Linux x64 4.19.0-9-amd64 <!-- generated by issue reporter --
Issue Type: <bBug</bIn the September release, we updated the suggest widget to respect the class. See The recent changes in the suggest widget for has caused a regression and brought the icons back when class is set on the widget. VS Code version: Code - Insiders 1.29.0-insider (, 2018-10-19T06:50:39.461Z) OS version: Darwin x64 15.6.0 <!-- generated by issue reporter --
I still see icons in the Setting suggest widget: !
I meant the settings search <img width="646" alt="screen shot 2018-11-02 at 10 15 38 am" src="https://user-"
<!-- 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.34.0 OS Version: Windows 10 Steps to Reproduce: terminal any command that makes any change of your current project directory after a while, like 'New Folder' action refreshing directory by the terminal command, 'New Folder' input will disappear and File Explorer remains inactive <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes !
This was also discussed in and apparently fixed in , but I'm still experiencing this. Steps to reproduce: to in settings. a file, and add the following contents: Ensure that there's an empty newline at the end. Save it. Then hit Undo. Nothing will happen. Hit Undo again, then it will work as expected. You can even hit Save multiple times, and each time will add one extra step to the Undo list. So hit Save 10 times, then you can hit Undo 10 times and nothing will happen. Could you take a look at this if possible?