Weekly GitHub Report for Vscode: February 24, 2025 - March 03, 2025
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.97.2
1.2 Version Information:
Released on February 12, 2025, this update for Visual Studio Code focuses on resolving issues identified in the "January 2025 Recovery 2" milestone, with detailed release notes available on the official website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
WebView editor can dispatch keybinding when workbench does already: This issue involves a bug in Visual Studio Code where the WebView editor dispatches a keybinding action even when the workbench has already executed it, causing unintended behavior such as tabs moving twice with a single shortcut key press. The problem is reproducible on macOS, particularly when switching between tabs using specific keybindings, and it appears to be related to a regression introduced in a recent update.
- The comments discuss attempts to reproduce the issue, with some users unable to replicate it on different operating systems, while others confirm it on macOS. A user provides a Go program to automate the reproduction of the bug, leading to the discovery that the issue involves the
Ctrl+Tabcommand being dispatched twice. The discussion concludes with the issue being moved to the appropriate team for further investigation. - Number of comments this week: 17
- The comments discuss attempts to reproduce the issue, with some users unable to replicate it on different operating systems, while others confirm it on macOS. A user provides a Go program to automate the reproduction of the bug, leading to the discovery that the issue involves the
-
Terminal opens slow: This issue reports a bug where the terminal in VS Code opens slowly, a problem that began after recent updates. The user provides detailed system information and mentions that the issue persists across different terminal types, such as Git Bash, Command Prompt, and PowerShell, on a Windows 11 system.
- The comments discuss potential causes and solutions, including checking terminal settings, disabling extensions, and examining user profiles, but these do not resolve the issue. A video comparison shows the problem is specific to the Insiders version of VS Code. A bisect command is suggested to identify the problematic build, and a commit range is provided, indicating a possible source of the regression.
- Number of comments this week: 11
-
Very large set of details in terminal suggestions for
Where-object: This issue highlights a bug in the terminal suggestions for theWhere-Objectcmdlet in PowerShell, where users are presented with an overwhelming list of variations due to the cmdlet's 32 parameter sets. The discussion revolves around the complexity of displaying these variations in a user-friendly manner, with suggestions to truncate or consolidate the information to improve readability.- The comments discuss the overwhelming nature of the
Where-Objectcmdlet's help documentation due to its 32 parameter sets. Suggestions include truncating the displayed information, aligning the presentation with other tools like TypeScript, and wrapping text in the IntelliSense window for better readability. However, it is noted that changing the help documentation format is not feasible due to the way PowerShell and its tools are designed. - Number of comments this week: 11
- The comments discuss the overwhelming nature of the
-
Extension corrupted: vsc-material-theme, equinusocio.vsc-material-theme: This issue involves a problem with the "vsc-material-theme" extension for Visual Studio Code, where deleting the extension leads to persistent error notifications and spam that the user cannot resolve. The user is seeking assistance to locate temporary data folders to clear information about the plugin and stop the spam, expressing gratitude for the product despite this being their first bug encounter in six years.
- Multiple users confirm the issue persists even after deleting the extension, with a suggested workaround involving manually removing the extension entry from the
extensions.jsonfile, which resolves the notification loop for some but not all users. - Number of comments this week: 11
- Multiple users confirm the issue persists even after deleting the extension, with a suggested workaround involving manually removing the extension entry from the
-
No output in Test Results panel debugging pytest from test explorer: This issue reports a bug where debugging a pytest from the test explorer in Visual Studio Code does not produce any output in the test results panel, output panel, or terminal, even when the test is designed to break on an assertion. The user has provided a sample test case and configuration settings, noting that the expected output is missing, and is seeking clarification on whether this behavior is intended or a bug.
- The comments discuss the default behavior of pytest capturing output and suggest using
-sor--capture=noto see print statements. The user clarifies they want output during debugging, which is not working as expected. Various contributors inquire about the user's setup and suggest checking configurations, including using alaunch.jsonentry with adebug-testpurpose. The user confirms that this workaround provides terminal output but not in the debug console or test results panel, indicating a partial resolution. - Number of comments this week: 11
- The comments discuss the default behavior of pytest capturing output and suggest using
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Opening Extremely Long URLs Causes Notification Popup to Overflow the Display: This issue describes a problem in Visual Studio Code where attempting to open an extremely long URL from the terminal using
Ctrl + Clickcauses the notification popup to overflow the display, making it impossible to interact with the popup. As a result, users are unable to confirm or cancel the action to open the external website, forcing them to shut down VS Code to resolve the situation. - Relative clickable links rendered in the document don't work on Windows: This issue is about a bug in Visual Studio Code where relative clickable links rendered in documentation comments do not function correctly on Windows, despite working on MacOS. The problem specifically affects plain links in comments, such as those pointing to local files, and has been open for over a year without resolution, indicating a potential regression or oversight in the software's handling of these links on the Windows platform.
- VSCode restarting devices periodically: This issue describes a bug in Visual Studio Code where peripheral devices such as the mouse, speakers, and keyboard intermittently freeze and restart, accompanied by the Windows "plug in" sound, indicating a temporary disconnection and reconnection. The problem has persisted for over a year, affecting users on Windows 10 with specific hardware configurations, and involves various extensions and system settings that might be contributing to the issue.
- Show Comments in TextMate Scope Inspector: This issue is about a feature request to enhance the Visual Studio Code (VSCode) TextMate scope inspector by displaying comments from the TextMate grammar files, which are currently only descriptive within the files themselves and do not provide external assistance. The proposal suggests that showing these comments in the scope inspector could serve as basic documentation for TextMate scopes, thereby improving the usability and understanding of token customizations for developers.
- Inspect Context Keys Should Open JSON File instead of logging to dev console: This issue addresses a feature request for the Visual Studio Code project, suggesting that the "Inspect Context Keys" functionality should open a JSON file within the editor instead of logging information to the developer console. The proposed change aims to enhance user experience by allowing users to search within the object directly in VS Code, providing a more efficient and user-friendly interface.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 313
Summarized Issues:
- Visual Studio Code Crashes and Performance Issues: Visual Studio Code users have reported various crashes and performance issues across different platforms and versions. These include crashes when running Java 21 applications on Ubuntu due to outdated snap environments, and performance problems such as high resource usage when connecting to Windows Subsystem for Linux (WSL). Users suggest updating environments and optimizing resource management to resolve these issues.
- Visual Studio Code Debugging and Extension Issues: Users have encountered bugs related to debugging and extensions in Visual Studio Code, such as the inability to open hyperlinks from the terminal, issues with text input, and problems with extensions like GitHub Copilot. These issues disrupt workflows and require troubleshooting to identify and resolve the underlying causes.
- Visual Studio Code Terminal and Shell Integration Problems: Several issues have been reported regarding terminal and shell integration in Visual Studio Code, including problems with shell integration activation, terminal suggestion features, and path completion. These issues affect the usability of the terminal and require improvements in shell integration and suggestion mechanisms.
- Visual Studio Code User Interface and Usability Concerns: Users have raised concerns about the user interface and usability of Visual Studio Code, such as issues with hover styling, text legibility, and the behavior of the "Accept All Incoming" option in the merge editor. These issues impact the user experience and require attention to improve interface consistency and usability.
- Visual Studio Code Feature Requests and Enhancements: There are numerous feature requests and suggestions for enhancements in Visual Studio Code, including the ability to customize log regex, improve terminal path suggestions, and support for streaming encoding and decoding. These requests aim to enhance the functionality and flexibility of Visual Studio Code for various use cases.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 302
Summarized Issues:
- Accessibility Issues: Accessibility issues in Visual Studio Code include problems with screen readers and keyboard shortcuts. Screen reader users face challenges such as the inability to copy images correctly and the failure of the Narrator to read tree view descriptions. Additionally, there is a request for more accessible one-hand keyboard shortcuts to accommodate users with temporary disabilities.
- Authentication and Sign-In Problems: Users experience various authentication issues in Visual Studio Code, including repeated authentication failures with GitHub and Azure Active Directory accounts. These problems are often linked to proxy settings, captive login windows, and the need to revert to classic authentication modes.
- Extension and Marketplace Issues: Problems with extensions in Visual Studio Code include difficulties uninstalling extensions and issues with extension handling logic. Users report that uninstall attempts result in no action, possibly due to mismatches between metadata fields and Marketplace UUIDs.
- Performance and Stability Issues: Performance issues in Visual Studio Code include application crashes, slowdowns, and memory leaks. Users report problems such as the application randomly crashing, significant slowdowns due to excessive processes, and memory leaks in features like the Timeline view.
- Terminal and Command Line Issues: Terminal issues in Visual Studio Code include problems with command execution and terminal suggestions. Users experience unresponsive terminals, incorrect path suggestions, and issues with terminal link hover features disappearing too quickly.
- Settings and Configuration Issues: Users face issues with settings and configurations in Visual Studio Code, such as unexpected behavior in settings search logic and problems with settings synchronization. These issues lead to cluttered search results and synchronization failures across different machines.
- Debugging and IntelliSense Issues: Debugging and IntelliSense issues in Visual Studio Code include problems with auto-completion and variable value displays. Users report that IntelliSense stops functioning after certain actions, and inline values are not displayed as expected in notebooks.
- Git and Source Control Issues: Git and source control issues in Visual Studio Code involve problems with Git commands and source control sections. Users experience issues such as Git commands failing in WSL environments and source control sections becoming unresponsive.
- Feature Requests and Enhancements: Users request various feature enhancements in Visual Studio Code, such as the ability to disable all AI features, support for editing SVG source code, and improved syntax highlighting in the Webview. These requests aim to improve user experience and functionality.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
VSCode Removing Extensions on its Own
- Toxicity Score: 0.55 (Frustration, critical tone, collective dissatisfaction, skepticism.)
- This GitHub conversation involves multiple users expressing frustration over VSCode's automatic removal of extensions without user consent. The original poster and subsequent commenters share a sentiment of annoyance and dissatisfaction, with a tone that is critical and demanding. The conversation is triggered by the unexpected behavior of the software, which users feel undermines their autonomy and professional judgment. There is a sense of solidarity among the users, as they collectively call for changes to the software's behavior. The discussion includes a mix of personal experiences, technical issues, and references to external sources, with some users expressing skepticism about the information provided by extension maintainers.
-
- Toxicity Score: 0.65 (Escalating frustration, aggressive language, unresolved issue.)
- This GitHub conversation involves multiple users discussing issues with a specific extension. User1 initially confirms the extension's unsafety, while User2 expresses frustration over the lack of an uninstall button. User3 is notably annoyed by persistent alerts and requests a permanent solution, tagging another user for assistance. User4 inquires about a resolution, and User5 provides a workaround, which User6 appreciates. However, User7's comment escalates the tension with aggressive language, indicating growing frustration with the unresolved issue.
-
- Toxicity Score: 0.65 (Frustration, defensive responses, escalating tone.)
- This GitHub conversation involves a user, Andrew Dzhigo, expressing dissatisfaction with a product transition, leading to a series of exchanges with another user, gjsjohnmurray, who suggests that the issues might be related to extensions. Andrew Dzhigo responds with frustration, emphasizing a lack of time to troubleshoot and criticizing the product's reliability. The tone escalates as Andrew insists on the responsibility of the product provider for the extensions, culminating in a firm stance against advertising unreliable products. The conversation is marked by Andrew's persistent dissatisfaction and a defensive tone from gjsjohnmurray.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. All other pull requests are grouped based on similar characteristics for easier analysis.
Pull Requests Opened This Week: 19
Key Open Pull Requests
1. require 'prompt files' synchronization to be explicitly enabled by users: This pull request addresses privacy concerns by requiring users to explicitly enable the synchronization of 'prompt files' in Visual Studio Code, ensuring that this feature is only activated through the settings sync configuration or enablement dialog.
- URL: pull/242360
- Merged: No
2. Support targeting multiple scopes in a theme with tree sitter: This pull request aims to enhance the Visual Studio Code project by enabling themes to target multiple scopes using Tree-sitter, as indicated by the commits that include support for this feature and subsequent test fixes.
- URL: pull/241703
- Merged: No
3. More reuse via abstract modified file entry: This pull request aims to enhance code reuse by introducing an abstract modified file entry, addressing issues #13692 and #13693 in the vscode-copilot project, and includes several commits such as updates, a branch merge, and a todo addition.
- URL: pull/242311
- Merged: No
Other Open Pull Requests
- Image Alignment and Padding/Margin Issues: This topic covers pull requests that address alignment and padding/margin issues of custom image attachments in the Microsoft VSCode project. The pull requests focus on fixing layout aspects to ensure proper display and integration of images within the editor.
- Code Completion and Inline Edit Enhancements: These pull requests aim to enhance the code completion lifecycle by allowing partial acceptance signals and extending the rejection handler to differentiate between explicit and implicit rejections. They also propose adding the inlineEdit state to the show handler to enable better handling and logging of inline completions and edits.
- Terminal Suggestion Bug Fix: This pull request addresses a bug in the terminal suggestion feature where unexpected completions were returned. It ensures exact matches for command completions and corrects the comparison between
specLabelandcommand.label.
- GPU Channel Performance Improvement: This pull request proposes enabling the GPU channel to operate asynchronously from the runtime to alleviate the blocking of the renderer's main thread. It adopts an upstream feature from Chromium 134, resulting in significantly improved performance metrics.
- macOS Policy Support Integration: This pull request aims to integrate macOS policy support into the Visual Studio Code project. It references issue #148942 and depends on another pull request from the vscode-policy-watcher repository.
- Theme and Indentation Issues: These pull requests address the issue of the Night Owl Light theme appearing excessively blue and incorrect character indentation in settings with line breaks. They modify styles to correct these visual discrepancies.
- C# onEnterRules Update: This pull request updates the C# onEnterRules in the Visual Studio Code extension to handle documentation comments more efficiently. It prevents the insertion of a line comment when a triple comment is detected and adds a rule for automatic insertion of
///.
- WinGet Configuration File Update: This pull request updates the location and extension of WinGet configuration files to be placed in a
.configdirectory with a.wingetextension. It allows users to launch the configuration directly from the file explorer by double-clicking.
- Local Extension File Writeability: This pull request addresses an issue by making local extension files writable during the zip creation process. It is referenced in issue #151543.
- Problem Generation During Edits: This pull request addresses the issue of pausing problem generation during edits, rather than merely hiding squiggles. It is a fix for issue #13744 in the vscode-copilot repository.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. All other pull requests are grouped based on similar characteristics for easier analysis.
Pull Requests Closed This Week: 262
Key Closed Pull Requests
1. fix various TPI discoveries: This pull request addresses various issues identified in TPIs by implementing multiple fixes and enhancements, such as activating the send button when paused, making the play/pause/send button trimodal, enabling pause for stable, showing paused indicators for incomplete requests, adjusting the default state for modified files, cleaning up attachment problem labels, adding icons to problem attachment pills, allowing multiple problem selections, making problem markers clickable, and fixing the addition of multiple problem pills with appropriate labeling, as detailed in the commits linked to specific issues in the VSCode and VSCode-Copilot repositories.
- URL: pull/241980
- Merged: 2025-02-25T23:34:06Z
2. status - chat tweaks: This pull request, titled "status - chat tweaks," involves modifications to the chat functionality in the Visual Studio Code project, including a specific enhancement to speed up the isManagedHoverTooltipMarkdownString feature, and was successfully merged on February 23, 2025.
- URL: pull/241620
- Merged: 2025-02-23T16:15:30Z
3. path - update to the node.js version we ship (20.18.2): This pull request updates the Node.js version used in the project to 20.18.2, as indicated by the title and the commit messages, and it was successfully merged into the main branch on February 24, 2025.
- URL: pull/241745
- Merged: 2025-02-24T20:01:38Z
Other Closed Pull Requests
- Chat Status Enhancements: This topic covers multiple pull requests that focus on improving the chat status feature in the Visual Studio Code project. The changes include tweaks to status indicators, the addition of quota indicators, padding fixes, and the use of bold text to enhance the user interface and functionality. These updates aim to provide a more intuitive and visually appealing chat experience for users.
- Notebook Diffing Improvements: Several pull requests address enhancements to the notebook diffing functionality in Visual Studio Code. These changes include relocating diffing helper functions, fixing memory leaks, and ensuring consistent hashing for notebook outputs. The goal is to improve the maintainability and performance of notebook diffing processes.
- Prompt and Command Enhancements: This topic includes pull requests that introduce new features and fixes related to prompts and commands in the Visual Studio Code project. Changes include enabling reusable prompts, adding a super key modifier for the 'use prompt' command, and ensuring documentation URLs are available in selection dialogs. These updates aim to enhance the functionality and usability of prompts and commands.
- Chat Functionality Adjustments: Multiple pull requests focus on refining the chat functionality within the Visual Studio Code project. These changes include making the chat status a control with a lifecycle, simplifying code, and ensuring chat sessions are restored correctly. The updates aim to improve the overall chat experience and maintainability.
- Bug Fixes and Performance Improvements: Several pull requests address bug fixes and performance improvements in the Visual Studio Code project. These changes include resolving issues with option values, fixing memory leaks, and enhancing the sorting functionality for deleted cells. The updates aim to improve the stability and efficiency of the project.
- pull/241395, pull/241682, pull/241667, pull/241684, pull/241725, pull/241774, pull/241784, pull/241798, pull/241799, pull/241804, pull/241847, pull/241874, pull/241877, pull/241885, pull/241901, pull/241908, pull/241911, pull/241914, pull/241917, pull/241931, pull/241935, pull/241940, pull/241947, pull/241953, pull/241974, pull/241977, pull/241984, pull/241986, pull/241987, pull/242000, pull/242002, pull/242013, pull/242014, pull/242017, pull/242018, pull/242019, pull/242021, pull/242023, pull/242025, pull/242028, pull/242030, pull/242031, pull/242037, pull/242038, pull/242042, pull/242044, pull/242045, pull/242052, pull/242053, pull/242054, pull/242056, pull/242060, pull/242061, pull/242062, pull/242065, pull/242080, pull/242084, pull/242085, pull/242086, pull/242088, pull/242090, pull/242091, pull/242098, pull/242104, pull/242108, pull/242115, pull/242117, pull/242126, pull/242127, pull/242133, pull/242139, pull/242141, pull/242152, pull/242154, pull/242169, pull/242171, pull/242175, pull/242180, pull/242186, pull/242189, pull/242190, pull/242194, pull/242197, pull/242199, pull/242200, pull/242203, pull/242207, pull/242210, pull/242214, pull/242216, pull/242220, pull/242225, pull/242228, pull/242229, pull/242238, pull/242246, pull/242247, pull/242252, pull/242253, pull/242263, pull/242264, pull/242269, pull/242274, pull/242278, pull/242280, pull/242282, pull/242286, pull/242291, pull/242292, pull/242293, pull/242294, pull/242296, pull/242299, pull/242301, pull/242307, pull/242308, pull/242310, pull/242312, pull/242314, pull/242317, pull/242324, pull/242325, pull/242327, pull/242332, pull/242343, pull/242347, pull/242361, pull/242362, pull/242012
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
chat - toggle from title if installed
- Toxicity Score: 0.55 (Frustration expressed, Defensive responses, Escalating tension.)
- This GitHub conversation involves a discussion between several users, including username1 and username2, where username1 expresses frustration over a solution proposed by username2 that did not work as expected. The tone of the conversation is initially collaborative but becomes tense as username1's dissatisfaction grows. Username2 responds defensively, which further escalates the tension. Other participants attempt to mediate and offer alternative solutions, but the conversation remains strained.
-
- Toxicity Score: 0.55 (Defensive responses, unresolved frustration, mediation attempts.)
- This GitHub conversation involves username1 expressing frustration over username2's implementation, which did not resolve the issue as expected. Username2 responds defensively, leading to a tense exchange. Other participants, username3 and username4, attempt to mediate and offer alternative solutions, but the tone remains strained.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| meganrogge | 261 | 13 | 50 | 235 |
| Tyriar | 218 | 11 | 97 | 206 |
| bpasero | 237 | 49 | 52 | 125 |
| gjsjohnmurray | 13 | 1 | 2 | 350 |
| TylerLeonhardt | 17 | 1 | 18 | 180 |
| jrieken | 115 | 18 | 21 | 59 |
| roblourens | 91 | 10 | 6 | 67 |
| legomushroom | 152 | 9 | 4 | 5 |
| albertosantini | 0 | 0 | 0 | 169 |
| lszomoru | 58 | 1 | 6 | 86 |