Weekly GitHub Report for Vscode: March 10, 2025 - March 17, 2025
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.97.2
1.2 Version Information:
Released on February 12, 2025, this version of Visual Studio Code focuses on resolving issues identified in the "January 2025 Recovery 2" milestone, with detailed release notes available on the official website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
As of our latest update, there are no active issues with ongoing comments this week.
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Opening Extremely Long URLs Causes Notification Popup to Overflow the Display: This issue describes a problem in Visual Studio Code where opening extremely long URLs from the terminal using "Ctrl + Click" causes the notification popup to overflow the display, making it impossible for users to interact with the popup. As a result, users are unable to confirm or cancel the action to open the external website, forcing them to shut down VS Code to resolve the situation.
- Relative clickable links rendered in the document don't work on Windows: This issue is about a bug where relative clickable links rendered in documentation comments do not function correctly on Windows, despite working on MacOS. The problem specifically affects plain links in comments, such as those pointing to local files, and there is uncertainty about whether this is a regression or a longstanding issue.
- VSCode restarting devices periodically: This issue describes a bug in Visual Studio Code where peripheral devices such as the mouse, speakers, and keyboard intermittently freeze and restart, accompanied by the Windows "plug in" sound, indicating a reconnection. The problem has persisted for over a year, affecting users on Windows 10 with specific system configurations and a variety of installed extensions.
- Show Comments in TextMate Scope Inspector: This issue is about a feature request to enhance the Visual Studio Code (VSCode) TextMate scope inspector by displaying comments from the TextMate grammar files, which are currently only descriptive within the files themselves and do not provide external assistance. The proposal suggests that showing these comments in the scope inspector could serve as basic documentation for TextMate scopes, thereby improving the usability and understanding of token customizations for developers.
- Inspect Context Keys Should Open JSON File instead of logging to dev console: This issue addresses a feature request for the VS Code project, suggesting that the "Inspect Context Keys" functionality should open a JSON file within the editor instead of logging information to the developer console. The proposed change aims to enhance user experience by allowing users to search within the JSON object directly in VS Code, providing a more efficient and user-friendly interface.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
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: 36
Summarized Issues:
- Microsoft Authentication Issues in Visual Studio Code: The 'msal' option for Microsoft authentication in Visual Studio Code is experiencing issues where retrieving a login session with a specified tenant ID fails. This problem contrasts with the classic mode, leading to discussions about expected behavior and potential regression related to multi-tenant authentication and MFA requirements.
- Performance and Startup Regressions: Visual Studio Code has encountered performance regressions, notably with the update to Electron 34 causing slower window opening times. Additionally, the terminal opens slowly after recent updates, with users unable to resolve the issue by disabling extensions or modifying settings.
- Bugs in Visual Studio Code Version 1.97.2: Several bugs have been reported in Visual Studio Code version 1.97.2, including errors with Settings Sync on Windows 11, Python code execution failures on Windows 10, and paste functionality not working on Linux. These issues highlight inconsistencies and unexpected behaviors across different operating systems.
- Extension and Feature Malfunctions: Users have reported malfunctions with Visual Studio Code extensions, such as Python, Jupyter, GitHub Copilot, and GitLens, particularly in WSL environments. Additionally, there are issues with the AI Copilot feature being accidentally enabled and the inability to disable auto code suggestions.
- Terminal and Editor Bugs: Visual Studio Code users have encountered various terminal and editor bugs, including incorrect terminal suggestion displays and unexpected terminal cursor resets. Additionally, there are issues with dragging and dropping VSIX files and the application crashing when closing tabs or renaming classes.
- Syntax Highlighting and UI Issues: The
tree-sittersyntax highlighting engine in Visual Studio Code fails to apply certain scopes correctly, affecting various code elements. Additionally, there are UI issues such as excessive padding in the Source Control view and the Welcome pane appearing despite user settings.
- Feature Requests and Enhancements: Users have requested features such as customizing log regex for filtering logs from multiple services and enhancing the VS Code API to allow extensions to access task status. These requests aim to improve flexibility and responsiveness in Visual Studio Code.
- Miscellaneous Bugs and Requests: Various other issues include the inability to sync in Visual Studio Code, problems with text display, and the need for better handling of trackpad highlighting on Mac. These issues reflect a range of user experiences and requests for improvements.
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.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.
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: 0
As of our latest update, there are no open pull requests for the project this week.
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: 6
Key Closed Pull Requests
1. High contrast gutter items: This pull request addresses issue #227619 by introducing two new theming variables to enhance the foreground and background contrast of gutter items in the editor gutter, drawing inspiration from the existing commenting widget's theming to ensure proper display across dark, light, high contrast dark, and high contrast light themes.
- URL: pull/240906
- Merged: 2025-03-12T10:07:23Z
- Associated Commits: 8c61a
2. Clarify that our character offsets are in utf-16 code units: This pull request clarifies that the character offsets in the API are measured in UTF-16 code units, aligning with standard JavaScript string behavior, to prevent potential misunderstandings regarding offsets being interpreted as bytes, code units, displayed characters, or code units including surrogate pairs.
- URL: pull/241522
- Merged: 2025-03-11T19:53:17Z
- Associated Commits: 33575
3. Resolve compiler errors that appear due to useDefineForClassFields: This pull request addresses compiler errors in the VSCode codebase related to the useDefineForClassFields TypeScript setting by manually resolving 500 errors over five hours, without enabling the setting in the base tsconfig file, to prevent backsliding and facilitate internal builds at Google, while ensuring all tests pass.
- URL: pull/241544
- Merged: No
- Associated Commits: 41eda
Other Closed Pull Requests
- Internal Grammars Update: This pull request aims to prevent users from manually using the
markdown_latex_combinedandcpp_embedded_latexgrammars by prefixing their names withinternal_only_. This ensures they are recognized as internal-only language IDs intended for embedded blocks in LaTeX files, maintaining compatibility with future updates to the LaTeX syntax.
- macOS Policy Integration: This pull request introduces support for macOS policy integration in the Visual Studio Code project. It addresses issue #148942 and depends on changes from another pull request in the vscode-policy-watcher repository.
- C# onEnterRules Update: This pull request updates the C# onEnterRules in the Visual Studio Code extension to prevent the automatic continuation of line comments when pressing enter within documentation comments. It modifies the rule to detect triple slashes (
///) and adds a new rule to automatically insert///when hitting enter inside a documentation comment.
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 |
|---|---|---|---|---|
| bpasero | 169 | 1 | 38 | 56 |
| meganrogge | 92 | 0 | 19 | 103 |
| Tyriar | 57 | 0 | 32 | 81 |
| gjsjohnmurray | 7 | 1 | 1 | 144 |
| jrieken | 47 | 0 | 17 | 29 |
| TylerLeonhardt | 1 | 0 | 12 | 72 |
| DonJayamanne | 70 | 0 | 1 | 5 |
| legomushroom | 64 | 0 | 4 | 2 |
| roblourens | 39 | 0 | 6 | 22 |
| joyceerhl | 50 | 0 | 8 | 4 |