Weekly GitHub Report for Vscode: May 05, 2025 - May 12, 2025 (12:01:51)
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.
-
Model Picker not providing checked state and pressing enter does not switch: This issue highlights a bug in the Visual Studio Code's Copilot Chat feature where the model picker does not provide a checked state, and pressing enter does not switch the model as expected. The user reports that the screen reader does not announce the current model selection, leading to confusion, and questions whether this behavior is by design.
- The comments discuss the confusion caused by the model picker not reflecting the current selection, with suggestions to improve accessibility by including a checked state in the ARIA label. There is also a discussion about keybindings and the behavior of toggling between chat and editor modes, with some users experiencing inconsistencies.
- Number of comments this week: 15
-
Environment variables with URLs are incorrectly encoded with escape sequences (e.g., ':' becomes '\x3a'): This issue involves a bug in VS Code version 1.100.0 where environment variables containing URLs are incorrectly encoded with escape sequences, such as colons being converted to
\x3a. This encoding error disrupts applications that rely on correctly formatted URLs, particularly affecting Django applications that require precise URL formatting for settings like CORS and CSRF.- Multiple users report experiencing the same issue across different environments, including Linux and Windows with GitBash, where environment variables and paths are incorrectly encoded. Some users suggest workarounds like manually fixing environment variables or using specific configurations in
dotenvlibraries, while others emphasize the need for a quick fix or reversion of the update. A potential solution involving changes toterminal.integrated.shellIntegration.environmentReportingis discussed, but it does not resolve the issue for everyone. - Number of comments this week: 15
- Multiple users report experiencing the same issue across different environments, including Linux and Windows with GitBash, where environment variables and paths are incorrectly encoded. Some users suggest workarounds like manually fixing environment variables or using specific configurations in
-
Remote SSH terminal not working on VS Code version: Code 1.100.0: This issue reports a bug in Visual Studio Code version 1.100.0, where the remote SSH terminal fails to function on a remote machine running Linux, despite the local machine being on Windows. The problem seems to be related to a potential race condition or extension compatibility issue, as downgrading to a previous version or removing certain extensions resolves the issue.
- Users report intermittent success with the SSH terminal, with one user identifying a specific extension causing the problem. Some users resolved the issue by removing the
~/.vscode-serverdirectory, while others found network issues to be the cause. A suggestion was made to use a CLI tool to identify the regression, but the issue was not present in the insider build. - Number of comments this week: 11
- Users report intermittent success with the SSH terminal, with one user identifying a specific extension causing the problem. Some users resolved the issue by removing the
-
Play sound when chat agent requires user attention: This issue is about implementing a sound notification feature in a chat application to alert users when a chat agent requires their attention, such as during tool confirmations or prompts to continue iterating. The sound should be pleasant, similar to a phone notification, and should only play if the current window does not have focus, without needing to align with other accessibility sounds.
- The comments discuss the timeline for delivering the sound, with a request for it to be available by May 15, though a later date is suggested for better preparation. There is a clarification that the sound will be the same as used for screen reader users but will be the default for non-screenreader users. The discussion also touches on naming the sound signal and finalizing the delivery date, settling on an early delivery on May 16.
- Number of comments this week: 8
-
Using
bindon athis.<method>referencing that method?: This issue questions the necessity and intention behind using thebindmethod onthis.<method>references in a specific TypeScript file within the Visual Studio Code project. The user is seeking clarification on whether this pattern is intended or if it is a leftover from previous code practices.- The comments discuss the rationale behind binding methods to
this, with some contributors explaining it was initially used to ensure correct method context when methods are passed by reference. Others argue against this pattern, suggesting it can lead to confusion and unnecessary overhead, proposing alternative solutions like binding at the usage point or using arrow functions. The conversation includes examples and counterarguments about performance implications and the potential for silent errors, with some contributors advocating for letting the user handle binding to maintain clarity and reduce complexity. - Number of comments this week: 8
- The comments discuss the rationale behind binding methods to
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 highlights a problem with using the${userHome}variable in a task command within atasks.jsonfile in Visual Studio Code, where it generates incorrect paths when the task type is set to "process". The incorrect path format results in an error stating that the terminal process could not be started because the path to the executable shell file does not exist, whereas using${env:USERPROFILE}instead of${userHome}produces 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.
- Dubugger automatically opens huge libraries: This issue describes a performance problem in Visual Studio Code where the debugger automatically opens large, bundled, or minified libraries, causing significant delays and blocking the process when syntax highlighting and linting are applied. The user experiences this issue primarily when working with TypeScript or JavaScript, as the debugger resolves to large files like extensionHost.js, making it cumbersome to close these files or continue working without restarting the application.
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: 205
Summarized Issues:
- Visual Studio Code Performance Issues: Performance problems in Visual Studio Code have been reported across different systems and versions, affecting basic operations like file creation and copy-pasting, as well as causing delays and unresponsiveness. These issues are often linked to system resource usage, extensions, and specific configurations, leading to user frustration and workflow disruptions.
- Visual Studio Code Update and Installation Bugs: Users have encountered bugs when updating or installing Visual Studio Code, with issues ranging from error messages during updates on macOS to problems with dependency installation in Azure DevOps pipelines. These bugs hinder the ability to maintain up-to-date software and can disrupt development processes.
- Visual Studio Code Debugging and Breakpoint Issues: Debugging in Visual Studio Code is affected by bugs where breakpoints do not trigger correctly, or the debugger fails to stop at the intended lines. These issues complicate the debugging process and can lead to inefficient troubleshooting and code analysis.
- Visual Studio Code Terminal and SSH Problems: The terminal in Visual Studio Code has been reported to malfunction, with issues such as SSH disconnections, terminal freezing, and incorrect path handling. These problems disrupt the development workflow, especially for users relying on remote development environments.
- Visual Studio Code Copilot and AI Integration Issues: Users have reported various issues with GitHub Copilot and AI integrations in Visual Studio Code, including malfunctioning chat features, incorrect suggestions, and performance problems. These issues affect the usability and reliability of AI tools within the IDE.
- Visual Studio Code Feature Requests and Enhancements: Numerous feature requests have been made to enhance Visual Studio Code, including improvements to the user interface, customization options, and new functionalities. These requests aim to improve the overall user experience and address specific needs of developers.
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: 176
Summarized Issues:
- GitHub Copilot Issues: GitHub Copilot in Visual Studio Code is experiencing multiple issues, including failing to retain context, causing crashes, and not locating necessary files in projects. These problems lead to user frustration as Copilot forgets recent interactions and fails to perform expected tasks, impacting productivity.
- Visual Studio Code Performance and Usability: Users report various performance issues in Visual Studio Code, such as freezing, slow response times, and unresponsive features. These issues are exacerbated by large workspaces and specific configurations, leading to significant workflow disruptions.
- Git and Source Control Problems: Visual Studio Code users face issues with Git integration, including unregistered source control providers and persistent Git error messages in non-Git workspaces. These problems hinder the ability to manage version control effectively within the editor.
- Extension and Feature Requests: There are numerous requests for new features and improvements in Visual Studio Code, such as better error explanation popups, enhanced extension management, and improved chat controls. These requests aim to enhance user experience and streamline workflows.
- Remote Development and SSH Issues: Users encounter critical problems with Visual Studio Code's Remote Development feature, including terminated processes and performance issues in SSH environments. These issues disrupt remote workflows and require troubleshooting to resolve.
- User Interface and Accessibility: Visual Studio Code's user interface presents challenges, such as overlapping buttons, missing scrollbars, and inconsistent padding. These issues affect accessibility and usability, prompting requests for UI improvements.
- Terminal and Command Execution: Problems with the integrated terminal in Visual Studio Code include improper display of stdout, execution failures, and persistent environment variables. These issues complicate command execution and terminal usage.
- Markdown and URI Handling: Visual Studio Code users report issues with markdown content limits and URI parsing errors. These problems affect the handling of large markdown files and the accuracy of URI operations within the editor.
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.
-
- Toxicity Score: 0.85 (Highly aggressive language, Single participant, No moderation or response.)
- This GitHub conversation involves a single user expressing extreme frustration and anger towards the development team, using aggressive and profane language to describe their dissatisfaction with the IDE's performance. The tone is highly negative and confrontational, with no other participants or responses in the conversation.
-
integrate the simple browser tool, already within the github copilot chat tools
- Toxicity Score: 0.75 (Aggressive language, Accusatory tone, Sudden escalation.)
- This GitHub conversation involves a user expressing a detailed feature request, followed by another user who responds with a highly aggressive and accusatory comment. The initial comment is neutral and focused on functionality, while the response introduces a confrontational tone, indicating a significant shift in sentiment.
-
- Toxicity Score: 0.55 (Frustration expressed, Criticism of delay, Repeated issue reports.)
- This GitHub conversation involves multiple users expressing frustration over a recurring issue with Microsoft account login in VS Code. The original poster, username1, expresses dissatisfaction with the persistent login prompts, while username2 and username3 provide links to related issues and suggest steps for further investigation. Username4 echoes the original complaint, and username5 criticizes the lack of a timely fix, indicating a serious bug persisting over several versions. The tone is generally frustrated and critical, with a focus on seeking resolution.
-
Copilot can't find files that are easily found
- Toxicity Score: 0.65 (Aggressive language, User frustration, Repeated misunderstandings.)
- This GitHub conversation involves a user expressing frustration towards GitHub Copilot's inability to locate a specific file, despite the user's insistence that the file exists. The user, identified as "Me," uses aggressive language when addressing Copilot GPT4.1, indicating a high level of frustration. Copilot GPT4.1 maintains a neutral and apologetic tone, attempting to assist by suggesting solutions and acknowledging the user's concerns. The tension is triggered by the user's belief that Copilot is not functioning correctly, leading to a heated exchange.
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: 21
Key Open Pull Requests
1. Defining variable fonts: This pull request focuses on implementing and testing the functionality of variable fonts in the Visual Studio Code editor, ensuring that various aspects such as line height, font size, text alignment, and rendering are correctly handled across different scenarios, including decorations, multi-line selections, and accessibility features.
- URL: pull/248410
- Merged: No
- Associated Commits: 03425, 88e55, d84a7, a2637, 82411, c54ab, a9806, 8a712, f4e5a, 8afcd, 6c110, 5ee48, 38dfb, d0685, f7ba2, f7d47, cf367, e3296, 91d4b, f7837, 25492, aaaad, 6395e, 549e9, 95f77, ce134, 9dec3, 952f8, 9f7b3, c6d8a, 6ab9c, 20d17, 54e89, e75e7, c7ce4, 13e7c, 5adde, 4ee17, b4b62, 4888a, 61dba, aae1f, 35b21, 295a5, 1e596, cdf87, 6ead1, 3414d, f06a2, 1e5a7, 1d64c, ed5fb, 5b066, b5991, 39256, b0b28, 9f5d1, 6f38e, 62d90, 9f044, 131cc, d1aec, ad4af, 71e1d, 1a44a, c5190, 904ec, 8a14e, 6a1d6, f2d01, 85989, 4ee90, 2b715, d37de, fc878, ba40a, 52056, dd305, 14a0f, 47d97, 891d4, 563ab, 3e914, b7c77, a72a0, 9c2ab, c2787, 52013, 97773, aebb4, 258e9, e66ae, 46c53, ea282, 50ec1, 244f8, 08511, 810ad, 33c3d, 2e751, fd68a, 6409b, 9764d, e7ee6, 30467, 5fbfa, fcd36, 65075, fb640, 0b24c, e59e8, 8c2e0, 6cbc9, 11754, 82e9b, 8a009, 4b2d3, 2b0bc, cf006, 5c662, d5443, 4425c, d6bfa, 07652, 2c677, 7f00f, ab923, 7e79a, d836d, 7a564, aa406, 686d4, 00a97, 7852d, 80f8f, 30609, 69048, 375f3, d188c, 02df0, 85934, 16156, 9ec92, 1840c, 0e1b5, 2ce71, 77403, 77c8c, f1996, 1e0e1, 75831, f4b05, 70e1d, 1d5fa, 19a81, 5ad6e, eda00, fc7d7, 13210, 486be, e16b5, 327dc, b9cc8, 9d58a, ff1f0, 148c8, 299b1, a41b8, 0acbd
2. [typescript-language-features] Add configuration for maximum hover length: This pull request introduces a new configuration option to the TypeScript language features in Visual Studio Code, allowing users to set a maximum length for hover text, and addresses issue #233557 while being linked to a corresponding TypeScript pull request.
- URL: pull/248181
- Merged: No
3. Bug/sticky scroll refactor 244845: This pull request involves refactoring the stickyScrollProvider.ts by simplifying and modularizing methods to reduce complexity, breaking down large methods into smaller, focused ones, adding JSDoc-style comments for improved readability and maintainability, and ensuring adherence to coding guidelines, all aimed at fixing issue microsoft/vscode#244845.
- URL: pull/248131
- Merged: No
Other Open Pull Requests
- Editor Decorations: This topic involves adding code to apply the same decorations to the left editor in the Visual Studio Code project. The pull requests focus on addressing excessive line height in decoration options and setting the correct line height for the empty text editor hint.
- Functionality Enhancements: These pull requests aim to enhance various functionalities within the Visual Studio Code project. They include enabling the attachment of logs to chat in a simple browser and introducing continuous selection of UI elements.
- Bug Fixes: Several pull requests address bug fixes in the Visual Studio Code project. These include resolving an unresolved setting ID in HTML settings, ensuring a custom line number is greater than
toLineNumberbefore deletion, and handling virtual drive paths on Windows subst drives.
- System Detection and Build Errors: These pull requests focus on system detection and resolving build errors. They enhance Linux system detection by including ChromeOS and address build errors caused by updated DOM types in TypeScript 5.9.
- Code Quality and Updates: This topic covers improvements in code quality and updates to the codebase. Pull requests include sorting import statements, updating the xterm.js library, and replacing OffsetEdit with StringEdit.
- Property Initialization and Proposal Removal: These pull requests address property initialization order and the removal of outdated proposals. They fix property initialization order in specific files and remove the
notebookCellExecutionStateproposal.
- RDP Scenario Fix: This pull request introduces a fix for repositioning maximized windows in an RDP scenario. It implements a workaround from the Electron issue tracker, controlled by a runtime argument for safer opt-in usage.
- HTML Course Addition: This pull request proposes the addition of a new HTML course to the project. It is currently open and not yet merged into the main branch of the Microsoft VSCode repository.
- Type Improvement: This pull request aims to improve the codebase by using a more appropriate type for the
ChatParticipantToolToken. It addresses issue #231937 in the Microsoft VSCode 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: 193
Key Closed Pull Requests
1. process - convert explorer to editor: This pull request involves converting the explorer functionality into an editor within the Visual Studio Code project, as indicated by the title and the main commit message, and it was successfully merged on May 6, 2025.
- URL: pull/248120
- Merged: 2025-05-06T15:21:02Z
- Associated Commits: ffb98, 3cd26, 59593, 42abb, 9e3d2, 52b6d, dcdbf, 766b0, 0996d, 63621, ff1af, 8e60a, c0d58, a85a9, da7d9, 4e9d4, 96817, 0ae65, 0a252, f2446, 327ca, 6f005, 1dea0, 53911, 5844e, 661f4, 7e29f, c2de4, ad207, 874a6, a9d88
2. [prompts][debt]: trace execution time of expensive methods of the prompt service: This pull request introduces a 'logTime' method decorator to trace and log the execution time of potentially expensive methods within the prompt service of the VSCode project, along with adding unit tests, improving documentation, and refining the computation of execution time for both synchronous and asynchronous methods.
- URL: pull/248144
- Merged: 2025-05-06T01:51:33Z
- Associated Commits: ca361, 86141, 78d81, a9c7c, 5d72a, b7421, 86705, 05bb9, 2ad0b, 7aaa0, 09074, a3b49, d338d, 6f7db, 458b4
3. refactor ui element selection to standalone service: This pull request refactors the UI element selection process in the Visual Studio Code project by moving it to a standalone service, addressing issue #247499, and includes multiple commits for restructuring code, fixing layer checker issues, and renaming services.
- URL: pull/248185
- Merged: 2025-05-07T08:24:24Z
- Associated Commits: 54980, 0ec35, ec85c, a0f80, e1341, 62108, 1b9bd, 15311, dcb9b, ad27b, 9caa9, d4f92, 42f19, 7cc63, e20c2
Other Closed Pull Requests
- Linter and Code Quality Enhancements: This topic covers the introduction of stricter linter rules, addressing linter errors, refactoring code to remove floating promises, and adding unit tests for the 'Stream' utility in the Microsoft VSCode project. These changes aim to enhance code quality and maintainability, as evidenced by multiple pull requests focusing on code improvements and documentation updates.
- Chat and Prompt Refactoring: This topic involves refactoring efforts in the chat setup and prompt files, including cleaning up the chat setup state and refactoring the ChatToolInvocationPart for better code organization. These changes improve maintainability and consistency across the Visual Studio Code project.
- Process Explorer Updates: This topic includes the removal of an outdated standalone window solution for the process explorer and the introduction of web support for this feature. These updates streamline the process explorer functionality and expand its accessibility within the Visual Studio Code project.
- Token and Type Improvements: This topic covers the introduction of a new "composite" token type and refactoring of the
equals()method across all token classes. These enhancements improve token composition and type safety, contributing to the overall robustness of the Microsoft VSCode project.
- MacOS Notification Behavior: This pull request implements a change in the macOS version of the app to bounce the dock icon instead of stealing focus when notifications are triggered. It addresses an existing issue and considers platform-specific nuances, such as a known Electron bug on Windows.
- Extension and Filter Enhancements: This topic involves the introduction of a new "Installed" filter to the Extensions view, allowing users to easily locate all currently installed extensions. It aligns with existing filters and reuses the
StaticQueryExtensionsViewfor consistent implementation.
- Notebook and URI Handling: This topic addresses issues with conflicting URI handling between the notebook editor and the notebook output preview editor. It implements additional filters to ensure correct resource support and editor selection, improving the overall functionality of notebook cell output management.
- Property Initialization and Refactoring: This topic covers the issue of property initialization order in specific files within the VSCode project, utilizing automated refactoring tools to prepare for upcoming changes. These efforts ensure consistent JavaScript output and improve code maintainability.
- Shell API and Git Bash Integration: This pull request addresses issues with the integration of Git Bash in the new shell API by correcting the invalid shell parameter and adjusting path parsing. It ensures the
_cachedExessize is checked to prevent empty results, enhancing the shell API's reliability.
- File Watcher and Extension Host Logging: This pull request involves logging the logic for the creation of file watchers by the extension host in the Visual Studio Code project. It was successfully merged, indicating improvements in monitoring and debugging capabilities.
- Environment Detection and Authentication: This pull request improves the logic for detecting whether the environment is a Node.js or web worker extension host. It includes enhancements related to Microsoft authentication and overall logic refinement, ensuring better compatibility and security.
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.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.
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 |
|---|---|---|---|---|
| legomushroom | 261 | 13 | 1 | 36 |
| bpasero | 167 | 24 | 46 | 65 |
| meganrogge | 54 | 5 | 27 | 154 |
| roblourens | 101 | 17 | 30 | 73 |
| jrieken | 87 | 10 | 22 | 59 |
| connor4312 | 68 | 8 | 11 | 87 |
| lszomoru | 84 | 11 | 11 | 29 |
| albertosantini | 0 | 0 | 0 | 117 |
| justschen | 61 | 7 | 4 | 34 |
| TylerLeonhardt | 17 | 5 | 16 | 58 |