Weekly GitHub Report for Vscode: March 24, 2025 - March 31, 2025 (12:05:31)
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.
-
Extensions not showing and says they load, but I can't see them: This issue involves a user experiencing problems with Visual Studio Code extensions not appearing in the extension list after upgrading from version 1.95.2 to 1.96.4. Despite uninstalling and reinstalling the extensions, they do not show up in the list, and the user encounters various warnings and errors in the window output, indicating potential issues with API proposals and authentication provider registration.
- The comments reveal ongoing troubleshooting efforts, including attempts to reinstall extensions, check logs, and adjust settings. The user reports that the extensions appear when using specific filters but not in the general view, and the issue persists despite reinstalling Visual Studio Code and clearing caches. The problem seems related to the extensions tab being stuck in a loading state, as indicated by a continuously moving blue bar.
- Number of comments this week: 16
-
VS Code Could not login to Azure: This issue involves a problem with logging into Azure through Visual Studio Code, where users encounter an error message related to consent configuration when attempting to sign in using the ChinaCloud instance. The error, identified as CAA20002, suggests a need for preauthorization configuration between the application and the resource, affecting users on Windows with VS Code version 1.98.2.
- The comments reveal that multiple users are experiencing the same login issue, with some providing screenshots for clarity. A team member acknowledges the problem and has opened an internal ticket with the Identity team to investigate further. Users are advised to open separate issues if they are not using the ChinaCloud instance, and the issue is identified as server-side, prompting escalation for resolution.
- Number of comments this week: 12
-
Prevent CustomEditor from Opening When a File is Opened from Search or GitLens: This issue addresses the problem of the
CustomEditorbeing automatically triggered for all*.jsfiles when opened from the search panel or GitLens in Visual Studio Code, which is not the desired behavior. The user suggests implementing agetContextAPI or awhenclause in thecustomEditorconfiguration to control when the editor should open, specifically to prevent it from launching when files are accessed from certain contexts.- A pull request has been raised to support the
whenclause incustomEditors, and multiple users have expressed that they are experiencing the same issue, emphasizing the need for this feature in future releases. - Number of comments this week: 11
- A pull request has been raised to support the
-
JS Debugger Companion extension installs itself?: This issue is about a user experiencing unexpected installations of the JS Debugger Companion extension in their Visual Studio Code environment, despite not having any JavaScript-related code or dependencies in their project setup. The user is seeking assistance to understand why this extension, along with others like ESLint and autopep8, is being installed automatically and how to prevent such installations when they are not explicitly defined in their
devcontainer.jsonconfiguration.- The comments discuss the unexpected installation of extensions, with suggestions to check the Dev Containers log and the extensions installation folder. It is noted that some extensions might be installed due to configurations in the base images or features of the dev container, and a method to exclude unwanted extensions by modifying the
devcontainer.jsonis provided. The user expresses concern about the clutter this might cause in their configuration file and seeks further clarification on the necessity of these automatic installations. - Number of comments this week: 10
- The comments discuss the unexpected installation of extensions, with suggestions to check the Dev Containers log and the extensions installation folder. It is noted that some extensions might be installed due to configurations in the base images or features of the dev container, and a method to exclude unwanted extensions by modifying the
-
No
onDidStartTaskProblemMatchersemited forStartStopProblemCollector: This issue is about a bug in a Visual Studio Code extension where theonDidStartTaskProblemMatchersevent is not emitted for theStartStopProblemCollector, despite theonDidEndTaskProblemMatchersevent working as expected. The user has provided steps to reproduce the issue, including creating a new extension and running specific tasks, but only the task end event is logged, suggesting a potential bug in the task problem matcher API.- The comments discuss whether the task has problem matchers, confirm that it does, and note that the issue persists even after a supposed fix. There is a mention of the problem occurring when there is no
execution, and a suggestion to verify the fix using both start-stop and watching problem matchers. - Number of comments this week: 8
- The comments discuss whether the task has problem matchers, confirm that it does, and note that the issue persists even after a supposed fix. There is a mention of the problem occurring when there is no
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 alongside markdown cells.
- 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 describes a problem in Visual Studio Code where using the${userHome}variable in a task command of type "process" results in incorrect path formatting, causing execution errors. The issue is specific to the "process" type and does not occur when using the "shell" type with PowerShell as the default shell, and a workaround involves using${env:USERPROFILE}instead of${userHome}to generate the correct path.- 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 issue with the remote connection entering a "sleep" state when the main window is minimized.
- 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 incorrectly as a question mark in Visual Studio Code. The problem persists even when all extensions are disabled, and the character displays correctly in other applications 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: 225
Summarized Issues:
- Feature Requests in Visual Studio Code: Several issues highlight requests for new features in Visual Studio Code, such as enabling an "expand all" feature in the Source Control sidebar, streamlining the process for updating extensions, and adding a setting to keep the terminal inline chat input visible. These requests aim to improve user experience by adding convenience and efficiency to existing functionalities.
- Bugs in Visual Studio Code: Various issues report bugs affecting Visual Studio Code's functionality, such as incorrect display of large integer keys in the Notebook Variables view, immediate appearance of code prompts, and misalignment of emojis in the integrated terminal. These bugs disrupt the normal workflow and require fixes to restore expected behavior.
- Visual Studio Code Debugging and Testing: Issues related to debugging and testing in Visual Studio Code include the need for displaying variable types in the hover UI and enhancing the Test Results panel to rerun only failed tests. These improvements aim to provide more detailed information and streamline the testing process for developers.
- Visual Studio Code Extension Issues: Several issues involve problems with extensions in Visual Studio Code, such as the C# Dev Kit extension failing to activate and the Python extension becoming non-functional. These issues hinder the use of extensions, which are crucial for extending the capabilities of the editor.
- Visual Studio Code UI and Usability: Issues related to the user interface and usability of Visual Studio Code include the need for a more informative notification system for image attachments and the suggestion to add a pin icon to the SCM status bar. These enhancements aim to improve the clarity and efficiency of the user interface.
- Visual Studio Code Performance and Stability: Performance and stability issues in Visual Studio Code include a crash related to tree-sitter and a problem with the application reopening itself after being closed. These issues affect the reliability of the editor and require attention to ensure a stable user experience.
- Visual Studio Code Syntax Highlighting: Several issues report discrepancies in syntax highlighting between stable and insiders versions of Visual Studio Code, affecting elements like CSS selectors and regular expressions. These inconsistencies can lead to confusion and require alignment across versions.
- Visual Studio Code Terminal Issues: Terminal-related issues in Visual Studio Code include problems with shell integration and the terminal suggestion feature stopping after clearing the terminal log. These issues disrupt terminal functionality, which is essential for many development workflows.
- Visual Studio Code Configuration and Settings: Issues related to configuration and settings in Visual Studio Code include the need for a configuration option to specify the installation path for extensions and a problem with the
vscode-merge-basesetting being duplicated. These issues affect the customization and management of the editor's environment.
- Visual Studio Code Copilot and AI Features: Issues involving GitHub Copilot and AI features in Visual Studio Code include a bug where Copilot incorrectly posts edits to the prompt and a request for Copilot to synchronize chat history across platforms. These issues and requests focus on improving the integration and functionality of AI tools within the editor.
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: 350
Summarized Issues:
- Visual Studio Code Bugs on macOS: Visual Studio Code on macOS has been experiencing several bugs, including a codesigning error when launching from the terminal and a regression affecting window dragging functionality. These issues disrupt the user experience by causing unexpected behavior and error messages, although some have been resolved in recent updates.
- Accessibility and Usability Enhancements: There is a need for improved accessibility features in Visual Studio Code, such as an Accessible Help feature for screen reader users and better handling of table formats in GitHub Copilot. These enhancements aim to make the software more inclusive by addressing the needs of users with disabilities and improving the overall user interface.
- GitHub Copilot and Chat Issues: Users have reported various issues with GitHub Copilot, including authentication problems, incorrect token errors, and malfunctioning chat features. These issues hinder the functionality of Copilot, affecting its ability to assist users effectively in their coding tasks.
- Terminal and Command Line Problems: The terminal in Visual Studio Code has been facing issues such as unresponsive commands, unexpected behavior with terminal profiles, and problems with command completions. These issues can disrupt the workflow of users who rely on the terminal for executing commands and managing their development environment.
- Performance and Stability Concerns: Visual Studio Code has been experiencing performance issues, including slow response times, crashes, and memory leaks. These problems affect the stability and efficiency of the software, making it challenging for users to maintain a smooth development process.
- Feature Requests and Enhancements: Users have requested various features and enhancements for Visual Studio Code, such as the ability to edit SVG files, support for PHAR files, and improvements to the Copilot status bar button. These requests aim to expand the functionality of the software and improve user experience.
- Integration and Compatibility Issues: There are ongoing issues with integration and compatibility in Visual Studio Code, including problems with the C# debugger not recognizing environment variables and the terminal process terminating unexpectedly on Windows. These issues can impede the development process by causing errors and limiting 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.
- Automation Test Bug 2
- Toxicity Score: 0.65 (Negative language,lack of constructive feedback)
- This GitHub conversation involves a single comment by an anonymous user expressing frustration with the website, using dismissive language. The tone is negative, and the comment lacks constructive feedback, which could trigger tension if others respond defensively or with similar language.
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: 30
Key Open Pull Requests
1. Engineering - switch over to the new build agents: This pull request involves transitioning to new build agents for the engineering process, including updates to the CLI stage agents, modifications to the macOS stage, and adjustments to ensure the node modules cache accounts for the agent's architecture, as detailed in the associated commits.
- URL: pull/244964
- Merged: No
2. prevent focus loss when More... menu closes for custom context menus: This pull request addresses an issue in the Visual Studio Code project where focus is lost when the "More..." menu closes in custom context menus on Windows and Linux, by ensuring the focus returns to the dropdown element, and includes several commits to refine the solution, such as focusing the dropdown element on menu close and using an exact delay.
- URL: pull/244990
- Merged: No
3. This PR adds support for when clauses in custom editor contributions, allowing developers to specify contextual conditions for when their custom editors should be available. #244703: This pull request introduces the ability to use "when" clauses in custom editor contributions within the Visual Studio Code environment, enabling developers to define specific contextual conditions under which their custom editors should be accessible, thereby enhancing the flexibility and control over editor availability based on the user's current context.
- URL: pull/244749
- Merged: No
Other Open Pull Requests
- Git Command Enhancements: This topic covers the introduction of a new
git.squashcommand and modifications to thegit.mergeAbortcommand to handle aborting squash merges. These changes address issue #243026 in the Microsoft VSCode project, enhancing the functionality of Git commands within the editor.
- UI and UX Improvements: Several pull requests focus on improving the user interface and experience in Visual Studio Code. These include introducing a 'hidden' option for the
titleScrollbarSizingparameter, correcting a dropdown option for disabling extensions, and modifying the Windows installer to streamline the Start Menu. These changes aim to enhance usability and address various user-reported issues.
- Source Control and Task Management: Enhancements to the Source Control Management (SCM) Graph and task management are addressed in these pull requests. They allow the default history filter to be configurable and ensure task start events are awaited before triggering problem matcher events, improving the workflow for developers.
- GitHub and Repository Management: Enhancements to GitHub publishing logic and handling renamed repositories are covered in these pull requests. These changes resolve issues where renamed repositories were incorrectly identified, preventing publishing, and improve the overall management of repositories.
- New Features and Actions: New features such as the "View Previous Edits" action and floating window support for MacOS are introduced. These features enhance the functionality and user experience by providing additional actions and window management capabilities.
- Bug Fixes and Code Improvements: Various bug fixes and code improvements are addressed, including fixing a bug with the WSL reconnection progress indicator, ensuring files are deleted properly when the recycle bin is disabled, and correcting a typographical error. These changes aim to improve the stability and accuracy of the codebase.
- Image and URL Handling: Improvements in image previews and URL handling are addressed, including resolving issues with URL encoding in fetch requests and modifying URI construction to prevent percent-encoding of reserved characters. These changes ensure better handling of media and URLs within the project.
- Chat and Panel Features: Enhancements to the chat feature and panel chat integration are explored, including integrating a completions provider and improving request forwarding mechanisms. These changes aim to enhance the interactivity and functionality of chat features within the editor.
- Semantic Tokens and Syntax Highlighting: Improvements to semantic token handling and syntax highlighting are addressed, including repairing invalid semantic tokens and ensuring SQL syntax highlighting in PHP is case-independent. These changes enhance the accuracy and consistency of code highlighting.
- Miscellaneous Enhancements: Various other enhancements include tracking user visibility of the NES interface, renaming code elements for clarity, and reintroducing parcel/watcher into compliance scans. These changes contribute to the overall improvement and maintenance of the project.
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: 239
Key Closed Pull Requests
1. Add AccountPolicyService: This pull request introduces the AccountPolicyService to the project, enhancing the existing MultiplexPolicyService by integrating both NativePolicyService and the new AccountPolicyService, and extends the DefaultAccountService to implement necessary business logic for account policies, allowing for the addition of policies for configurations not present in the core by updating the product.json file with new extension configuration policies.
- URL: pull/244315
- Merged: 2025-03-24T23:35:48Z
- Associated Commits: 685d6, a3256, e4c11, cf1e0, acc7f, c5416, 5f026, 96880, 759d0, acde8, 3f975, f3331, 93d83, 063be, 5ba93, 4d66b, d8d52, 043e4, 7ec84, 01fba, d2422, 76a27, 6ab42, f2091, adca8, 8ec61
2. drag and drop from external URLs: This pull request addresses issues #240025 and #242039 by implementing a feature that allows users to drag and drop content from external URLs into the application, with various improvements and cleanups made throughout the development process, as evidenced by multiple commits such as re-adding drag and drop functionality, enhancing data handling, and ensuring compatibility with shared processes.
- URL: pull/243816
- Merged: 2025-03-24T20:10:30Z
- Associated Commits: e75e9, 5a353, e43dc, 95ced, 61808, 98fc2, 9d769, 84e64, 82c3c, a5e78, 48776, 4ee30, 49f3e, 71fb9, 7b8a9, 7dcb5, b751a, ca80c, 89167, f16bb, 31363, 727b9, 26ac4, 2b18e
3. apply existing label, doc, and detail to inline completion : This pull request addresses issue #244486 by applying existing labels, documentation, and details to inline completions in the Visual Studio Code project, ensuring functionality for built-in features and executables, and includes multiple commits for bug fixes, code consolidation, and improvements based on code review suggestions.
- URL: pull/244490
- Merged: 2025-03-24T22:21:17Z
- Associated Commits: 8211d, 27cd4, 368aa, 10e91, 24a7d, 2f6f7, 0b49f, 00ea7, 6222c, 6eac9, 0a507, ea9f4, 3b3ee, 8dcc9
Other Closed Pull Requests
- Copilot Feature Enhancements: This topic covers improvements to the Copilot feature in Visual Studio Code, including the ability to attach notebook cell outputs as context in chat requests and the introduction of "action" buttons to manage current prompts. These enhancements include output URI parsing, support for image outputs, and updates such as using symbols for modifier keys on Mac to save space and keeping the prompt selection dialog open during delete confirmation.
- Drag and Drop Improvements: This topic addresses improvements in handling drag and drop operations within Visual Studio Code, specifically setting DragData for directories and fixing web-related URL handling. These changes ensure directories are correctly handled in drag data operations and improve logging practices to avoid using the console.
- Tunnel Specifications and Server Management: This topic involves resolving issues related to tunnel specifications and server management in Visual Studio Code, including fixing subcommand options and adding an 'add' button to the server list. These updates also address issues with servers continuing to run after being removed from configuration and refine test expectations.
- Unresponsive Windows and Diagnostics: This topic focuses on addressing unresponsive windows in Visual Studio Code by implementing logging of JavaScript stack traces and enhancing error telemetry. These changes improve diagnostics and debugging capabilities by adding CLI support to control the sample period.
- Terminal Suggest Path and Telemetry: This topic covers updates to the terminal suggest path executable cache and resolving telemetry issues related to terminal suggestions. These changes include updating the cache whenever there is a change in the binary and fixing existing telemetry problems.
- TypeScript and Type Updates: This topic involves updating Visual Studio Code to use the latest TypeScript version, addressing necessary updates to
@types/node, and fixing various type errors. These updates also resolve issues related to layer checks and CSS client extension types.
- View Container and UI Improvements: This topic addresses issues with view containers displaying no view if the default view is removed and introduces a new proposal for a chat status API. These changes include several commits for cleanup, type adjustments, and making UI tweaks.
- Browser Testing and Setup Updates: This topic enables the ability to run tests in either Chrome or Microsoft Edge browsers and addresses a signing issue with the Inno Setup updater. These updates include adopting a channel in tests and reapplying a previous update to resolve the signing issue.
- Shell Integration and Prompt Reporting: This topic adds shell integration properties to the
terminal/createInstanceevent and introduces simple prompt type reporting for common prompt frameworks. These changes improve PowerShell preview reporting and add more prompt type cases.
- Markdown Preview and Error Fixes: This topic addresses a fix for handling images with CORS errors in the markdown preview and resolves a "Maximum call stack size exceeded" error. These changes ensure images are copied correctly and prevent infinite recursive calls triggered by variable reuse.
- PlzDedicatedWorker and Cell Index Adjustments: This topic covers the re-enabling of the PlzDedicatedWorker feature and adjustments to cell indexes when inserting a new cell. These updates ensure proper functionality and synchronization of internal IDs for new cells.
- Third-Party Tools and Progress Message Fixes: This topic introduces a quick fix for third-party tools to display a confirmation message and addresses the inconsistency between progress messages. These changes include setting auto-confirmation allowances and restoring the progress message to the top in Ask mode.
- Server Picker and Syntax Highlighting Updates: This topic introduces a feature to add an "add server..." option to the select tools picker and involves updating the JavaScript Regular Expressions syntax highlighting file. These updates also include making certain items non-pickable and were not merged into the main branch.
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.
- try fixing https://github.com/microsoft/vscode-copilot/issues/13299
- Toxicity Score: 0.55 (Frustration expressed, Defensive responses, Escalating tension.)
- This GitHub conversation involves several users discussing a proposed fix, with username1 expressing frustration over the lack of progress and username2 responding defensively. The tone shifts from collaborative to tense as username3 attempts to mediate, but username1's continued dissatisfaction escalates the tension.
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 | 224 | 50 | 35 | 308 |
| bpasero | 231 | 90 | 44 | 163 |
| roblourens | 181 | 100 | 19 | 138 |
| Tyriar | 84 | 54 | 41 | 193 |
| connor4312 | 130 | 71 | 40 | 129 |
| sandy081 | 49 | 47 | 9 | 163 |
| jrieken | 74 | 50 | 23 | 81 |
| lszomoru | 69 | 46 | 10 | 96 |
| deepak1556 | 46 | 20 | 8 | 128 |
| TylerLeonhardt | 29 | 23 | 7 | 126 |