Weekly GitHub Report for Vscode: March 31, 2025 - April 07, 2025 (12:05:40)
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.98.2
1.2 Version Information:
Released on March 12, 2025, this update for Visual Studio Code focuses on resolving issues identified in the February 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.
-
(Insider) Error while handling chat request: Already handling this request: This issue involves an error encountered when attempting to use the agent mode in GitHub Copilot's chat feature within Visual Studio Code Insiders, where the system returns an error message indicating that the request is already being handled. The problem seems to be related to organizational settings that disable certain preview features, including agent mode, which the user needs to enable for the feature to function correctly.
- The comments discuss troubleshooting steps, including checking login status, adjusting settings, and reviewing logs. Users share their experiences and solutions, such as enabling specific settings and organizational policies to resolve the issue. A fix is proposed to prevent users from selecting modes disabled by organizational policy, and an update is expected to remove the preview feature check for agent mode.
- Number of comments this week: 11
-
Considerable Input Delay After 1.99: This issue reports a significant input delay and performance degradation in Visual Studio Code version 1.99.0, particularly noticeable in large repositories, which was initially thought to be related to the VSCodeVim plugin but was later identified as a problem with the base editor itself. The user provides detailed system and workspace information, highlighting that the problem is difficult to reproduce in smaller workspaces but is severe enough to make the editor nearly unusable in larger projects.
- Multiple users report similar performance issues with version 1.99.0, especially in large projects, and discuss potential workarounds such as rolling back to a previous version. Some users express frustration and consider switching to alternative editors due to the lack of an easy rollback feature in VSCode, while others suggest adding such a feature to the editor.
- Number of comments this week: 10
-
Code inside of #ifdef is darkened, even though the constant is defined: This issue is about a problem in Visual Studio Code where code inside an
#ifdefdirective is displayed in a darkened color, making it difficult to read, even though the constantHAVE_VIDEO4LINUX2is defined. The user is questioning whether this behavior is intentional or a bug, as the code should be readable regardless of whether the condition is met.- The comments discuss whether the constant
HAVE_VIDEO4LINUX2is defined, with users examining the code and configuration files to verify its definition. There is a clarification on how the constant is defined based on certain conditions, and a user confirms that the code works for them. Another user provides a link to the complete source code, and it is noted that a specific file might be generated during the build process. - Number of comments this week: 8
- The comments discuss whether the constant
-
Keyboard arrows do not work on Lenovo Tablet and they told me to ask here: This issue involves a problem with keyboard arrow functionality on a Lenovo Tablet when using a code-server setup, where the user experiences erratic cursor behavior while editing files. The user has confirmed that the issue persists even when all extensions are disabled and has been advised by code-server staff to report the issue here if it can be reproduced in codespaces.
- The comments reveal that the user was initially directed by code-server staff to report the issue here if it could be reproduced in codespaces. A discussion ensues about whether the issue can be reproduced using the official VS Code server, and the user confirms that the problem persists with both digital and physical keyboards. The issue is acknowledged, and the appropriate team is assigned to investigate further.
- Number of comments this week: 6
-
Exclusão de linhas não autorizadas: This issue is about a bug where the user experiences unauthorized deletion of multiple lines of code when attempting to create a modal window, which results in the application becoming non-functional. The user reports this problem occurring repeatedly and provides details about their system and software versions to aid in troubleshooting.
- The comments section includes requests for a screen recording to better understand the issue, guidance on how to attach files via the GitHub web interface, and a suggestion to close the issue due to the user's difficulty with GitHub. There is also a query about whether the problem is related to GitHub Copilot Chat and how the user interacts with it.
- Number of comments this week: 6
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.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request for Visual Studio Code to support the generation and display of markdown from code cells, similar to how JupyterLab handles dynamic content in its Outline feature. The request highlights the need for an option to render markdown generated by code cells in the output, allowing for dynamic titles and content to be displayed, enhancing the functionality and user experience in VS Code.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue describes a bug in Visual Studio Code where using a
vscode://link with the parameters?new-windowor?reuse-windowdoes not function as expected, as it hijacks the existing window instead of opening a new one. The problem occurs when a user is connected to a remote server and attempts to open a link to another server, resulting in the disconnection from the current server and replacement of the window with the new server's connection. ${userHome}in a task command creates bad paths: This issue involves a problem with the${userHome}variable in a task command within atasks.jsonfile, which results in incorrect path formatting when the task type is set to "process". The incorrect path causes an error stating that the terminal process could not be started because the path to the executable does not exist, whereas using${env:USERPROFILE}instead of${userHome}resolves the issue by generating the correct path format.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where characters typed in a terminal window, when moved to a floating window during a remote connection, do not appear in real time if the main window is minimized. The characters only become visible once the main window is restored, suggesting a potential "sleep" state in the remote connection that prevents real-time updates.
- Unicode character displayed as a question mark ?: This issue involves a problem where a Unicode character, specifically the full-width quotation mark (U+FF02), is displayed as a question mark when copied into Visual Studio Code (VS Code). The problem persists even when all extensions are disabled, and the character displays correctly in web browsers like Firefox, indicating a rendering issue within VS Code itself.
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: 222
Summarized Issues:
- Feature Requests in Visual Studio Code: Users have submitted various feature requests to enhance the functionality of Visual Studio Code. These requests include the ability to use predefined variables within the
setting.jsonfile, implement a draggable modal pop-up window, and allow customization of the position of individual custom panels. Additionally, users have requested features like a folding feature forgit commitmessages, a line-wrap mode that wraps text by a strict character count, and a global option to disable the reuse of task terminals. These enhancements aim to improve user experience and workflow efficiency.
- Bugs in Visual Studio Code: Several bugs have been reported in Visual Studio Code, affecting its functionality and user experience. These include issues with the "preview on GitHub" button not functioning, an error message when opening SVG files, and the default keybinding
Ctrl+K Ffailing to close the workspace. Other bugs involve the JAWS screen reader not deactivating its virtual cursor, the "Changes" view shifting unexpectedly, and the high contrast theme on the activity bar being inconsistent. These bugs disrupt the normal operation of the software and require attention for resolution.
- Performance Issues in Visual Studio Code: Users have reported performance issues in Visual Studio Code, such as laggy scrolling in Jupyter Notebooks, high CPU usage on MacOS, and the application freezing on Microsoft Dev Box. These issues affect the efficiency and usability of the software, prompting users to seek solutions or revert to previous versions to mitigate the problems. Performance optimization is crucial to ensure a smooth and responsive user experience.
- Accessibility Challenges in Visual Studio Code: Accessibility issues have been identified in Visual Studio Code, particularly affecting users who rely on screen readers. Problems include misalignment between VoiceOver and keyboard focus, incorrect announcements by JAWS and NVDA, and the lack of visible focus indicators. These challenges hinder the ability of users with disabilities to navigate and interact with the software effectively, highlighting the need for improved accessibility features.
- GitHub Copilot and AI Integration Issues: Users have encountered issues with GitHub Copilot and AI integration in Visual Studio Code. These include the inability to track AI-generated changes with undo/redo functionality, performance problems with automatic code generation, and bugs in the Copilot Chat feature. Additionally, there are requests for improvements in AI assistant performance and the introduction of a signal sound notification for task completion. Addressing these issues and requests is essential for enhancing AI-driven development workflows.
- Visual Studio Code Extension and API Enhancements: There are proposals to enhance the Visual Studio Code API and extension capabilities. Suggestions include allowing programmatic saving of documents without formatting, improving the MCP tool invocation process, and enabling extensions to identify the source of command triggers. These enhancements aim to provide developers with more flexibility and control over their extensions and improve the overall development experience.
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: 352
Summarized Issues:
- Consolidation of Functions in Codebase: This issue involves consolidating multiple functions (
pushText,pushNotebookCellText,pushNotebook) into a single function (pushEdit) to streamline the handling of edits in the codebase. The focus is on ensuring consistent message formats and reducing the need for backward compatibility.
- Copilot Chat Feature Bugs: Several issues describe bugs in the Copilot Chat feature of Visual Studio Code, including an "Invalid Input" error with the
#changeskeyword and rendering problems with HTML tags. These bugs affect usability across different versions and operating systems, but some were resolved with updates.
- March 2025 Iteration and Endgame Plans: The iteration plan for March 2025 for the Visual Studio Code project outlines a 4-week work period focusing on integrating GitHub Copilot as a standard feature. It includes specific tasks across various areas and sets endgame dates for completion.
- Context Picker and Quick Pick Menu Issues: A problem occurs in the VSCode project where selecting the
fileoption from the context picker using a mouse results in the quick pick menu closing immediately. This makes it appear as if no action has been taken, affecting user interaction.
- File Reference Clickability During Streaming: In the Visual Studio Code project, file references are not clickable during the streaming of a chat response. This renders any attempt to click on them ineffective until the response is fully received, impacting user experience.
- VS Code Insiders Editor Copy Bug: A bug in the VS Code Insiders editor causes selected text to be automatically copied to the clipboard, disrupting the user's workflow. This behavior differs from the expected requirement of an explicit copy command and does not occur in the production version.
- Tree-sitter Feature Reload Requirement: A problem in the Microsoft VSCode project requires a reload the first time the tree-sitter feature is enabled. This issue is indicated by the title and the lack of additional details or comments in the provided JSON data.
- Git Branch Creation Validation Request: A feature request for Visual Studio Code suggests implementing a pre-execution validation check for Git branch creation. This would notify users if a branch with the same name already exists, improving efficiency and aligning with other IDEs.
- Debug Console Autocomplete Bug: A bug in Visual Studio Code's debug console causes selected suggestions from the autocomplete list to append to the already typed text instead of replacing it. This results in duplicated text, except when typing after a dot character.
- Settings Synchronization Failure: A bug in Visual Studio Code affects the synchronization of the
git.defaultCloneDirectorysetting. Despite attempts to sync it through the Settings UI, the setting is incorrectly negated in thesettingsSync.ignoredSettingsconfiguration.
- Copilot Edits Tab Feature Request: A feature request for Visual Studio Code suggests adding an "Open in new window" option to the Copilot Edits tab. This would improve workflow and screen space management by allowing users to view and manage suggested edits in a separate window.
- Extension Signature Verification Performance: The slow performance of Extension Signature verification in the Windows Subsystem for Linux (WSL) on Ubuntu 22.04.5 LTS is discussed. Potential causes and suggestions for capturing logs to diagnose the problem are provided.
- Webview Component Memory Leak: A memory leak in the webview component of Visual Studio Code involves a leaked disposable object tracked by the
GCBasedDisposableTracker. This causes errors during the creation and resolution of webview views.
- High CPU Usage on macOS with M1 Chip: A performance problem with Visual Studio Code causes 100% CPU usage on a system running macOS with an Apple M1 chip. The high CPU usage is linked to the "Code Helper" process, affecting features like IntelliSense.
- Cursor Visibility Bug: A bug in Visual Studio Code causes the cursor to temporarily become invisible when it moves over a typeable area if the cursor is set to a reversed color. This affects user interaction and visibility.
- Extension Issue Reporting: A user-reported problem related to extensions in Visual Studio Code lacks sufficient details and a descriptive title. The user is prompted to provide more information and follow the contributing guidelines.
- Test List Button Update Issue: In a Visual Studio Code extension, test list buttons are not updated automatically when a TestRunProfile is disposed. Manual intervention is required to refresh the icons, despite the presence of a listener.
- File Tab Right-Click Bug on Ubuntu: A bug in Visual Studio Code on Ubuntu 24.04.2 LTS causes all other open tabs to close when right-clicking on a file tab. This problem does not occur in the previous version of the software.
- Unnecessary Files in Distributable Package: The inclusion of unnecessary files and directories in the distributable package of a project is discussed. The potential need to exclude additional files to ensure a cleaner distribution is highlighted.
- Duplicate Workspace Extension Recommendations: A problem in Visual Studio Code involves the same workspace extension being recommended multiple times. This issue is indicated by the title and the accompanying screenshot link.
- Custom Label File Extension Bug: A bug in Visual Studio Code's custom label feature incorrectly identifies the file extension by considering all characters after the first period in a file name. This affects the correct identification of the extension.
- TypeScript Intellisense Performance Issue: A performance problem in Visual Studio Code causes TypeScript Intellisense to be persistently stuck on "Analyzing file and its dependencies." This severely affects the editor's performance and renders Intellisense non-functional.
- Tool Confirmation Dialog Cut Off: A problem in a software application causes the tool confirmation dialog to be cut off, preventing users from clicking the button with a mouse. This is likely due to very long commands.
- Attach by Process ID Feature Issue: A problem with Visual Studio Code on Windows 11 prevents users from attaching to a process using the "Attach by Process ID" feature. This is due to the absence of
wmic.exe, which has been deprecated and removed in recent Windows updates.
- Search Results Issue on exFAT32 USB Drive: A problem in Visual Studio Code prevents files and folders with underscores in their names from appearing in search results when using an exFAT32 formatted USB drive.
- Request Retry Handling Issue: A problem occurs where retrying a request that involved multiple tool calls does not result in any actions being handled by the Agent in the UI. This ultimately reaches a turn limit without any visible outcome.
- Command Palette Permanently Open Bug: A bug in Visual Studio Code version 1.98.2 on Windows causes the Command Palette to remain permanently open and unclosable. This persists even after reinstalling the application.
- Grammatical Error in Output Window: A grammatical error in the Visual Studio Code application displays the string "1 older results" instead of "1 older result" in the "Show Output" window.
- Recurring Crash on Raspberry Pi OS: A recurring crash in Visual Studio Code version 1.98.2 on Raspberry Pi OS 64-bit causes the application to terminate unexpectedly with a crash code '5'. Users find temporary relief by downgrading to version 1.97.2.
- Blurry Interface Issue: A problem in Visual Studio Code causes a blurry interface, and users are prompted to verify if the issue persists when all extensions are disabled. Instructions for troubleshooting are provided.
- MCP Server Name Caching Issue: The caching of the MCP server name in Visual Studio Code causes the action bar to display the old server name despite updating the server URL in the settings.json file.
- Relative Path Recognition Issue: Visual Studio Code fails to recognize images and videos when referenced through a relative path, as reported in a GitHub project.
- JavaScript Navigation Issue: A problem in Visual Studio Code prevents users from navigating to specific method locations within a project after it is opened, affecting JavaScript functionality.
- Unwanted File Opening on Launch: A bug in Visual Studio Code causes a new file named "Untitled-1.ipynb" to automatically open every time the application is launched. The user seeks a solution to prevent this behavior.
- macOS 10.15.7 Support Request: A user requests continued support for macOS 10.15.7 in Visual Studio Code, as the latest version requires macOS 11.0 or higher. This causes inconvenience due to the user's inability to upgrade their operating system.
- Scrolling Bug in VS Code Insiders: A bug in the latest version of VS Code Insiders causes scrolling in the editor window to hide lines of source code instead of properly scrolling through the code.
- CSS Syntax Highlighting Issues: Several issues highlight problems with CSS syntax highlighting in Visual Studio Code, including ID selectors, universal selectors, and pseudo-element selectors not being rendered correctly in the Dark+ theme.
- Tree Sitter Syntax Highlighting Issues: Problems with Tree Sitter syntax highlighting in Visual Studio Code include incorrect coloring of escape sequences and look-around expressions in regular expressions.
- GitHub Copilot Markdown Editing Bug: A bug in Visual Studio Code causes GitHub Copilot to unexpectedly stop editing markdown files containing fenced code blocks. Instead, it outputs its remaining edits to the chat window.
- Chat Feature Output Focus Issue: A problem in a GitHub project causes the chat feature to discuss the entire notebook instead of focusing solely on the output of a specific cell when queried.
- VS Code Remote Server Start Failure: An exception is thrown by the handler due to a failure in starting the VS Code remote server, specifically affecting GitHub Codespaces. Changing the region to the US resolved the issue for some users.
- Chat Command Display Bug: Executing the 'Add Cell Output to Chat' command in a Visual Studio Code project fails to display or reveal the Chat view when it is hidden.
- Profiles Context Menu Display Issue: Ensuring that the profiles context menu in a GitHub project displays all possible actions, including inline actions, is discussed. There is a concern about potential duplicates with primary actions.
- Task Execution Event Handling Bug: A bug in a Visual Studio Code extension prevents the
onDidStartTaskProblemMatchersevent from being emitted for tasks using theStartStopProblemCollector. TheonDidEndTaskProblemMatchersevent functions correctly.
- MCP Server Start Failure Error Indicators: The lack of clear error indicators when an MCP server fails to start due to a missing API key in the environment variables is discussed. The server starts and then stops without providing an obvious reason for the failure.
- Nested Selector Color Rendering Discrepancy: A discrepancy in color rendering for nested selectors between the stable and insiders versions of Visual Studio Code is observed in the chat.css file.
- Color Rendering Discrepancies in CSS: Several issues highlight discrepancies in color rendering between the stable and insider versions of Visual Studio Code, affecting animations, custom properties, and media selectors.
- Screen Reader Accessibility Issues: Several issues address the lack of aria alert notifications for screen reader users when toggling between different chat modes and models in a project. This affects accessibility and user experience.
- Configuration Key Name Inconsistency: An inconsistency in configuration key names for MCP servers between VS Code and other documentation is discussed. Alignment is suggested to reduce the need for manual adjustments.
- CodeLens Request Frequency Configuration: A configuration option in VS Code to limit the frequency of
textDocument/codeLensrequests sent to a language server is suggested. This would reduce unnecessary processing and better align with command-line tool outputs.
- SQL Query Execution Error Handling: A problem in Visual Studio Code causes SQL query execution errors to require manual clicking on "Messages" to view the error. This differs from SQL Server Management Studio, where the error is displayed immediately.
- Dialog Button Activation Confusion: The
dismissOnLinkClickfeature in dialogs causes confusion about which dialog button was activated. Suggestions include using theAUX_WINDOW_GROUPoption to open files in a new floating window for better clarity.
- CORS Errors with Server-Sent Events: Server-Sent Events (SSEs) can intermittently fail due to Cross-Origin Resource Sharing (CORS) errors. Explicitly ordering delegates to prioritize running in the Node.js extension host is suggested.
- Python Package Import Errors on macOS: After installing MacOS 15.4, import errors with Python packages such as Pandas and Plotly occur due to a problem with importing the numpy dependency, despite the packages being installed in the environment.
- Transient Editor Reappearance Bug: Transient or preview editors, when opened in an auxiliary window, incorrectly reappear in the main window upon closure instead of being dismissed entirely.
- Publisher Information Cut Off Bug: A bug in Visual Studio Code causes the publisher's information to be cut off when the "Restart Extensions" button appears after an update. This is particularly noticeable when the interface is resized.
- SVG File Mode Switching Command Request: A command or button to facilitate easier switching between preview mode and text mode for SVG files in the project is requested.
- Gemini 2.0 Flash Model Bug: A bug in the Gemini 2.0 Flash model used in VS Code causes nonsensical and repetitive responses filled with the character "दट" and other random text. This indicates potential data poisoning or a problem with the model's training data.
- Source Code Management View Performance Issue: A performance problem in Visual Studio Code causes the interface to get stuck when attempting to view the content of changed files in the source code management view. This requires the user to forcibly close the application.
- Completions Status Indicator Update Bug: A bug in Visual Studio Code causes the completions status indicator to fail to update appropriately when the language mode of a file is changed, despite the initial status being correctly displayed.
- Memory Leak with File Protocol: A memory leak problem in Visual Studio Code occurs when using the file protocol, specifically due to duplicate operations triggered by the "Go to Reference" option in the right-click menu.
- Built-in Terminal Abort Signal Bug: The built-in terminal in the Apple Silicon build of Visual Studio Code does not respond to abort signals after running a program that aborts. This occurs consistently on the second attempt and does not affect the Intel chip version.
- Accessibility Combo Box Labeling Issue: An accessibility problem in Visual Studio Code causes the programmatic name for the "Select subscriptions" combo box to not match its visual label. This causes difficulties for screen reader and speech input users.
- Invalid Webview ID Regression: An invalid webview ID encountered when loading worker resources in a project regressed due to a specific pull request. Steps for verification involving the Postman VS Code extension are included.
- Environment Variable Reference Support Request: A request for support for referencing environment variables using the
${env:VARIABLE_NAME}syntax in themcp.jsonfile is made. This would enhance configuration flexibility in the project.
- Terminal Suggestions Malfunction in WSL: Terminal suggestions malfunction when using the Windows Subsystem for Linux (WSL) with the Kali Bash terminal on Windows, as reported in the Visual Studio Code GitHub repository.
- API Changes and Authentication Provider Events: Proposed changes to an API include replacing
AccountwithSession, introducing events for registering and unregistering authentication providers, and discussing the separation ofloginandgetSessionsfunctions.
- MCP Server Start/Stop Command Confusion: The start/stop commands for servers in the MCP feature of VS Code cause confusion. Improvements such as auto-starting servers after adding them and simplifying the commands to "Refresh" are suggested.
- Diff System Enhancement Request: A feature request for Visual Studio Code suggests enhancing its diff system by allowing users to save and focus on differences between files of different languages. This would improve efficiency and clarity in multilingual projects.
- AI-Generated Content Cultural Bias Concern: A concern about AI-generated content from GitHub Copilot is raised, as it is perceived to predominantly reflect the cultural narrative of the Islamic Republic of Iran. A solution is called for to ensure fair representation free from political bias.
- Go Formatter Disabling Request: The lack of a straightforward option in the Microsoft VSCode Go plugin to disable Go formatting is highlighted. A simple list entry for disabling the formatter without resorting to JSON configuration is requested.
- Unified JDK Configuration Request: The challenges of developing Java projects in VSCode are discussed, specifically the need for a unified JDK configuration across various Java extensions to improve functionality and user experience.
- Smoke Test Timeout Error: A smoke test failure in Visual Studio Code's Electron version occurs due to a timeout error during the verification of restored opened editors. This indicates a potential problem with asynchronous test execution or promise resolution.
- Python Script Execution Freeze: A performance problem in Visual Studio Code Insiders on a Windows system causes a Python script to freeze and not terminate even after pressing
Ctrl+C. A fix for this problem is requested.
- Source Control Tab Crash: A problem in Visual Studio Code causes the application to crash on the Source Control tab when attempting to view a file diff. This requires a force quit to resolve and persists even when all extensions are disabled.
- Explorer View Visibility Bug: A bug in Visual Studio Code prevents users from viewing folders or files in the explorer view, despite disabling all extensions. The problem was resolved by deleting the code folder in the Windows app data.
- Chat Interface Scrollbar Appearance: A scrollbar appears in a chat interface when multiple requests are sent, raising questions about whether it is intentional for the current request to always appear at the top while still showing a portion of the previous response.
- IPv6 Support for Port Forwarding: The lack of IPv6 support when attempting to forward a port in Visual Studio Code results in an error message. This issue has been identified as a duplicate of another issue.
- C++ IntelliSense Method Suggestion Issue: A problem in Visual Studio Code causes the IntelliSense feature to fail to display method suggestions for C++ code. The user desires a list of suggestions without auto-completion, only appearing upon selection and confirmation.
- MCP Server Interaction User Experience: Improved user experience in managing MCP server interactions within VS Code's Copilot Chat is suggested. Enhancements include single-click icons for starting, stopping, and restarting servers, as well as providing instant feedback on server status.
- GitHub Copilot Nonsensical Code Generation: A bug in Visual Studio Code causes GitHub Copilot to generate nonsensical and repetitive code, leading to confusion and a crash. The user expresses a need for better control over the AI's actions.
- C# Application Launch Configuration Bug: A bug in Visual Studio Code prevents a user from launching a simple C# application using the F5 key due to a missing configuration in 'launch.json'. This results in a popup error and console errors.
- High CPU Usage in Large Workspaces: A performance problem in Visual Studio Code causes high CPU usage in large workspaces with numerous TypeScript watched folders. Proposed solutions include implementing a debounce mechanism and distributing watch requests over time.
- Test Issue via API: Several test cases were created through API testing on the Microsoft VSCode GitHub repository. These issues were generated to verify functionality and are documented with minimal details.
- File Save Extension Bug: A bug in Visual Studio Code version 1.98.2 on Windows 10 causes the software to automatically append a .txt extension when attempting to save a file without an extension. This is contrary to the user's intention.
- Java Test Detection Issue: A bug in Visual Studio Code prevents JUnit tests from being detected in a Java project. The "Run Test" and "Debug Test" buttons do not appear in the editor, despite the tests running successfully from the terminal.
- Node-Related Service Execution Stuck: A performance problem on a Mac Sequoia system causes the user to be stuck during the execution of node-related services such as npm and yarn installations. This occurs while using Visual Studio Code version 1.98.2 on an Apple M1 chip.
- Localization Problem in Extract to Function Feature: A localization problem in Visual Studio Code causes the phrase 'your input' to not be translated into Simplified Chinese (CHS) after using the "Extract to function" feature.
- Maximum Call Stack Exceeded Error: A "Maximum call stack exceeded" error is encountered in a Git diagnostics commit hook when attempting to commit with over 1000 errors present in the Problems view.
- W Key Malfunction on Windows 10: A performance problem in Visual Studio Code version 1.98.2 on a Windows 10 system causes the "W" key to not work, affecting the user's ability to type words containing the letter "W".
- E2E Issue via Playwright UI Test: Several test scenarios were generated by Playwright UI tests on the Microsoft VSCode GitHub repository. These issues were created to evaluate functionality and are documented with minimal details.
- issues/245448, issues/245449, issues/245451, issues/245453, issues/245455, issues/245457, issues/245461, issues/245462, issues/245463, issues/245464, issues/245465, issues/245466, issues/245467, issues/245468, issues/245469, issues/245470, issues/245472, issues/245473, issues/245474, issues/245475, issues/245476, issues/245477, issues/245478, issues/245479, issues/245480, issues/245481, issues/245482, issues/245483, issues/245484, issues/245485, issues/245486, issues/245487, issues/245488, issues/245489, issues/245490, issues/245491, issues/245493, issues/245494, issues/245495, issues/245496, issues/245497, issues/245498, issues/245499, issues/245500, issues/245501, issues/245503, issues/245504, issues/245505, issues/245506, issues/245507, issues/245508, issues/245509, issues/245511, issues/245512, issues/245513, issues/245515, issues/245516, issues/245517, issues/245518, issues/245520, issues/245521, issues/245522, issues/245523, issues/245525, issues/245526, issues/245527, issues/245528, issues/245529, issues/245530, issues/245532, issues/245533, issues/245534, issues/245535, issues/245536, issues/245537, issues/245538, issues/245539, issues/245541, issues/245542, issues/245543, issues/245544, issues/245545, issues/245546, issues/245547, issues/245548, issues/245549, issues/245550, issues/245551, issues/245552, issues/245553, issues/245554, issues/245555, issues/245556, issues/245557, issues/245558, issues/245559, issues/245560, issues/245562, issues/245563, issues/245568, issues/245569, issues/245575, issues/245577, issues/245580, issues/245581, issues/245582, issues/245583, issues/245584, issues/245585, issues/245586, issues/245587, issues/245588, issues/245589, issues/245590, issues/245591, issues/245592, issues/245593, issues/245594, issues/245597, issues/245599, issues/245600, issues/245601, issues/245602, issues/245603, issues/245604, issues/245605, issues/245606, issues/245609, issues/245611, issues/245612, issues/245622, issues/245626, issues/245628, issues/245639, issues/245642, issues/245659, issues/245661, issues/245674, issues/245679, issues/245680, issues/245681, issues/245682, issues/245683, issues/245684, issues/245685, issues/245686, issues/245687, issues/245691, issues/245693, issues/245696, issues/245714, issues/245716, issues/245722, issues/245725, issues/245727, issues/245753, issues/245760, issues/245762, issues/245766, issues/245770, issues/245775
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.
-
如果我fork之后，换个LOGO和主题，那是否违反了许可证？我想做vscode换皮IDE，可以吗？
- Toxicity Score: 0.65 (Confrontational tone, aggressive language, lack of resolution.)
- This GitHub conversation involves a user expressing frustration over perceived spam, which is met with defiance by another user. The tone is confrontational, with one user insisting on continuing their actions despite the request to stop. The conversation includes aggressive language and a lack of resolution, indicating a potential for further conflict.
-
vscode is not language friendly，I can't breath
- Toxicity Score: 0.55 (Dismissive response, Tense interaction, Potential for escalation.)
- This GitHub conversation involves a user expressing dissatisfaction with a software issue, while another user responds with a dismissive comment, indicating frustration with perceived spam. The tone of the conversation is tense, with the initial post being a formal bug report and the response being informal and potentially aggressive.
-
Copilot trial expiration spams msg too frequently
- Toxicity Score: 0.55 (Repeated frustration, unresolved issue, negative tone.)
- This GitHub conversation involves multiple users expressing frustration over a recurring issue, with user1 and user2 showing particular dissatisfaction with the persistence of a notification. The tone is predominantly negative, with users feeling that the issue is not being addressed adequately. User3 attempts to provide a solution by redirecting the issue to another platform, which does not seem to alleviate the frustration. The conversation is marked by a sense of urgency and dissatisfaction, with users feeling ignored and overwhelmed by the problem.
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. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 28
Key Open Pull Requests
1. Engineering - background codesign for Windows stage: This pull request involves engineering efforts to implement background codesign for the Windows stage in the Visual Studio Code project, including the addition of a zx package, various task and script updates, performance improvements, and attempts to run signing processes in parallel.
- URL: pull/245796
- Merged: No
- Associated Commits: 6dd1c, 5fa21, 9f993, 991ee, 1f766, 95385, ac60b, 61c6b, 792e4, c6547, 22d6e, 8be21, 7ab8e, 3b0c3, 40ac5, 616fc, 62920, eb308, 1e2c1, d97c6, ec0f5, 5ccdc, 967a3, 90e5d, f3b2e, 8ea76, 55a27, e3c6a, 24f74, b9a9c, eafa1, cb0ed, 25229, 0e3f2, cd13f, dbf7b, 0d4bc, 2b1c5, ba25b, 8d21f
2. chore: update to Electron 35: This pull request involves updating the Visual Studio Code project to use Electron version 35, addressing issue #245420, and includes several commits such as bumping Electron to versions 35.0.1 and 35.1.2, updating Node.js types and web types to version 22.x, modifying the Node.js build, temporarily bumping the distribution, and updating the app.dock usage in reference to a specific Electron commit.
- URL: pull/245423
- Merged: No
3. Feature: don't show error peek overlay when navigating over errors (next/prev error by F8 hotkey): This pull request introduces a feature that allows users to disable the error peek overlay when navigating through errors using the F8 hotkey by adding a showOverlay option to the ZoneWidget and a new problems.gotoError.showOverlay setting, addressing issues #51787 and #63591.
- URL: pull/245092
- Merged: No
Other Open Pull Requests
- Visual Studio Code UI Enhancements: Several pull requests focus on improving the Visual Studio Code user interface. These include updates to the CSS styling of the extensions viewlet's search container for better accessibility, introducing secondary border styles for buttons, and adding a 'Find Files in Explorer' button to enhance user convenience.
- Bug Fixes in Visual Studio Code: Multiple pull requests address various bugs in Visual Studio Code. These include fixing a white flash issue when opening the app maximized on Windows, correcting indentation issues in TypeScript files, and resolving a bug where ':' inside a CSS comment block incorrectly triggers a suggestion.
- Accessibility and Theme Improvements: Pull requests have been made to enhance accessibility and theme consistency in Visual Studio Code. These include addressing an accessibility issue in the high contrast theme of the activity bar and ensuring consistent visibility of hover and active outlines across all icons.
- Feature Additions and Enhancements: New features and enhancements have been proposed in several pull requests. These include introducing a draft feature for
scopeOverrideCustomText, a proof of concept for reverting a task status API, and allowing thesavemethod to accept an optionalSaveOptionsargument.
- Codebase and Configuration Updates: Various pull requests focus on updating the codebase and configurations. These include migrating away from
*.experimental.*tree sitter settings, renaming configuration files, and removing brokentokenTypesto improve code handling.
- Minor Corrections and Typo Fixes: Several pull requests address minor corrections and typo fixes in the Visual Studio Code project. These include fixing a single-character typo in a JSON file and correcting a typo in the command-line interface update.
- Open and Unmerged Pull Requests: There are several open and unmerged pull requests, including one titled "Praevt" and another involving the creation of a new feature named "NewAbdullah." These requests are still under review and have not been integrated into the main branch.
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. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 220
Key Closed Pull Requests
1. Engineering - PR pipeline improvements: This pull request involves a series of updates and improvements to the pull request pipeline for the Visual Studio Code project, including modifications to the Windows test job, updates to the PR pipeline, setup of various stages for different operating systems (Linux, macOS), and adjustments to artifact publishing tasks, although it was ultimately not merged.
- URL: pull/245309
- Merged: No
- Associated Commits: 77026, d6244, 979d0, 7edac, 5ae4c, eb11b, 43899, e2bc8, adb0e, 2323d, e9574, 18aee, d4726, 65d22
2. Engineering - run tests based on target: This pull request, titled "Engineering - run tests based on target," was merged on April 3, 2025, and involves running tests grouped by specific targets such as electron, browser, and remote, with multiple commits addressing various aspects like refactoring stages for Linux, Windows, and macOS, changing job order, updating parameters, fixing artifact names, and commenting out Electron smoke tests for Windows.
- URL: pull/245367
- Merged: 2025-04-03T06:27:23Z
3. ESM for extensions: This pull request introduces native ECMAScript Module (ESM) support for extensions in the Node.js extension host of Visual Studio Code, allowing extensions to use import statements when they indicate ESM support via type: module or the .mjs suffix, and enabling import('vscode') functionality similar to require('vscode'), while also supporting ESM extension tests, as detailed in the associated issue https://github.com/microsoft/vscode/issues/130367.
- URL: pull/245214
- Merged: 2025-04-01T09:08:33Z
Other Closed Pull Requests
- Engineering Pipeline Improvements: This topic covers enhancements to the engineering pipeline, including reorganizing jobs into stages and refining test artifact handling. Pull requests involved removing commented-out code, tweaking job order, updating CI build definitions, and addressing macOS-specific changes.
- Application Health Mechanism: This topic involves implementing a mechanism to terminate the Electron application if it is in an unhealthy state. Pull requests included logging the application's alive state upon exit and printing all relevant times.
- Copilot Edits View Removal: This topic focuses on the removal of the Copilot Edits view from the Visual Studio Code project. Pull requests involved deleting related configurations, context keys, and helper functions, as well as eliminating associated actions and UI elements.
- Build Agent Transition: This topic covers transitioning to new build agents for the engineering process. Pull requests included updates to CLI stage agents, modifications to the macOS stage, and adjustments for node modules cache based on agent architecture.
- Focus Issue Fix: This topic addresses an issue where focus was lost when the "More..." menu closed in custom context menus on Windows and Linux. Pull requests ensured focus returns to the dropdown element and refined the solution with an exact delay.
- Tencent.yml File Creation: This topic involves the creation of a file named "tencent.yml" which was ultimately not merged. Pull requests included fixing PHP highlighting code blocks and bumping the version of "tar-fs."
- Policy Service Testing: This topic addresses testing the
AccountPolicyServiceandMultiplexPolicyServicein the VSCode project. Pull requests added boolean configurations, corrected typos, and incorporated composed services into tracked disposables.
- Unit Test Parallel Execution: This topic aimed to enhance the testing process by implementing parallel execution of unit tests. Pull requests included switching to using npm run and running tests in parallel, though it was not merged.
- Internationalization of Tooltip Text: This topic addresses the internationalization of the tooltip text for the "Close Banner" button. Pull requests ensured localization for different languages, resolving issue #245194.
- Chat Feature Enhancements: This topic introduces support for actions related to status headers in the chat feature. Pull requests included enhancing hover functionality for images and cleaning up the chat widget.
- IChangeTracker Interface Integration: This topic integrates functions into the
IChangeTrackerinterface. Pull requests aimed at fixing continuous integration (CI) issues.
- Task Start Event Timing Issue: This topic addresses issue #244625 by ensuring the task start event is awaited before triggering the problem matcher started event. Pull requests included multiple commits to fix and refine the solution.
- ESLint Rule for Internal Imports: This topic introduces an ESLint rule to ensure only sibling files of "internal" source code folders can import from them. Pull requests prevent deep imports and allow specific import paths.
- Code-Tunnel Tests Addition: This topic, titled "add
code-tunneltests," was merged and includes multiple commits aimed at fixing issue #244886. Pull requests added additional tests and cleaned up the code.
- Auxiliary Window Configuration: This topic addresses issue #245162 by modifying the application to open the "to-trust" configuration in an auxiliary window. Pull requests detailed the change and were successfully merged.
- Working Set Cleanup: This topic involves cleaning up remnants of the working set in the Visual Studio Code project. Pull requests focused on removing working set elements and addressing assumptions about document entries.
- Electron Framework Update: This topic involves updating the Electron framework to version 34.4.0. Pull requests included several commits related to this version bump and temporary distribution updates.
- Agent Mode Setting Registration: This topic involves registering the agent mode setting by default on the stable version of the project. Pull requests included initial registration, fixing comments, and making the implementation safer.
- Technical Debt Resolution: This topic addresses a technical debt by fixing the initialization order of class properties. Pull requests resolved issue #243049 and were successfully merged.
- Image Handling Improvements: This topic focuses on improving the quality of life and cleaning up image handling within the project. Pull requests included better previews, renaming, and code cleanup.
- Non-Recursive File Watching Performance: This topic focuses on enhancing performance for non-recursive file watching. Pull requests were successfully merged and indicated by the title and commit messages.
- View Previous Edits Feature: This topic introduces a new feature titled "View Previous Edits." Pull requests added the action and enhanced functionality by finding the first stop containing the URI.
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.
-
Remove EditingSession location
- Toxicity Score: 0.55 (Defensive responses, critical feedback, tense exchange.)
- This GitHub conversation involves username1 who initiates the discussion with a proposed change, while username2 provides feedback that is initially neutral but becomes increasingly critical. Username1 responds defensively, leading to a tense exchange. The tone shifts from collaborative to confrontational, with both parties expressing frustration.
-
ensure spec descriptions come through
- Toxicity Score: 0.55 (Defensive responses, critical feedback, unresolved tension.)
- This GitHub conversation involves user 'devUser1' who initiates the discussion with a proposed fix, while 'reviewer2' provides feedback that is initially constructive but becomes increasingly critical. 'devUser1' responds defensively, leading to a tense exchange. 'contributor3' attempts to mediate by suggesting a compromise, but 'reviewer2' remains firm in their stance, causing further friction. The tone shifts from collaborative to confrontational, with 'devUser1' expressing frustration over perceived misunderstandings.
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 |
|---|---|---|---|---|
| bpasero | 262 | 40 | 51 | 95 |
| meganrogge | 199 | 8 | 28 | 172 |
| roblourens | 206 | 20 | 18 | 98 |
| connor4312 | 139 | 20 | 44 | 108 |
| jrieken | 98 | 17 | 20 | 66 |
| lszomoru | 126 | 14 | 8 | 47 |
| Tyriar | 75 | 3 | 38 | 75 |
| deepak1556 | 62 | 8 | 10 | 67 |
| i-stefan-1994 | 0 | 0 | 131 | 0 |
| alexr00 | 72 | 16 | 7 | 33 |
Don't miss what's next. Subscribe to Weekly Project News: