Weekly GitHub Report for Vscode: April 07, 2025 - April 14, 2025 (14:15: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.
-
MCP Tool Dropdown UX Improvements: This issue focuses on improving the user experience of the MCP Tool Dropdown and Confirmation Card in Visual Studio Code, aiming for implementation by the April 2025 milestone. The proposed enhancements include introducing a first-time server run confirmation card, adding more information to the tool dropdown's closed state, using human-readable tool names, wrapping long content in a collapsible UI, and polishing the overall tool dropdown UI for better clarity and usability.
- The comments discuss various aspects of the proposed UX improvements, including concerns about the verbosity of warnings, the timing of server run confirmations, and the discoverability of tool details. Suggestions include removing the first-time server run confirmation card to avoid approval-blindness, making tool details more visible, and considering the removal of the cancel button to streamline user interactions. There is a consensus on the need for these improvements, with some debate on the best way to implement them while maintaining a smooth user experience.
- Number of comments this week: 15
-
Very slow performance when making changes: This issue reports a significant decline in performance when making changes in Visual Studio Code, particularly after updating to version 1.99.1, with users experiencing slowdowns in various operations such as saving files, using Git, and pasting text. The problem seems to be exacerbated on macOS systems with Apple M1 chips, and users have noted that downgrading to version 1.98 temporarily resolves the issue.
- Users have shared profiling reports and noted that the slowdown began after a recent update, affecting various functionalities like saving and pasting. Many users confirmed experiencing similar issues, with some suggesting downgrading to an earlier version as a temporary fix. There are also references to related issues that might be connected to this performance problem.
- Number of comments this week: 14
-
VSCode on Windows does not resolve environment variables unless started from a terminal: This issue describes a problem with Visual Studio Code (VSCode) on Windows, where environment variables are not resolved correctly when the application is started from the OS native launcher, leading to failures in pre-commit hooks that depend on these variables. The user reports that this problem does not occur when VSCode is started from a terminal, suggesting that the application does not respect the default shell startup profile in GUI mode as it does on macOS and Linux.
- The comments discuss the expected behavior of VSCode regarding environment variables, with suggestions to manually set the
pnpmpath in system variables. The user clarifies that this is not feasible due to the need to switch NodeJS versions usingfnm. A workaround involving a Batch wrapper forpnpmis proposed, and the user suggests that VSCode should implement environment resolution on Windows similar to macOS and Linux. - Number of comments this week: 13
- The comments discuss the expected behavior of VSCode regarding environment variables, with suggestions to manually set the
-
Endlessly asking to log in, it never stops!: This issue is about a persistent bug in Visual Studio Code version 1.99.0 on Windows 10, where users are repeatedly prompted to log in without success. The problem seems to be related to authentication settings, and users have attempted various fixes, including changing authentication implementation settings and adjusting browser configurations, but the issue persists.
- Users are experiencing repeated login prompts in VS Code, with some suggesting a temporary fix by reverting to a deprecated authentication method. Logs indicate issues with token caching and account recognition, and a request for trace logs was made to gather more information. An internal issue has been opened to escalate the problem.
- Number of comments this week: 9
-
MCP: Expose current git remote as root: This issue discusses the need to expose the current Git remote as a root in the Model Context Protocol (MCP) to enhance functionality tied to the remote, as the current setup only supports
file://roots. The proposal suggests that having the MCP server automatically recognize the GitHub remote could improve operations like custom code search, CI/CD, and observability without relying on potentially unreliable client-provided information.- The comments explore the potential benefits and challenges of exposing the Git remote as a root, noting that while it could enhance certain functionalities, the current restriction to
file://roots limits its utility. Some users express interest in experimenting with this feature to assess its impact, while others highlight the complexity of handling multiple remotes and suggest that a Git-aware MCP server could address more complex use cases. There is also a discussion about the evolving nature of root contexts beyond just files, indicating a space for further exploration. - Number of comments this week: 7
- The comments explore the potential benefits and challenges of exposing the Git remote as a root, noting that while it could enhance certain functionalities, the current restriction 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 that allows code-generated markdown to be rendered and displayed after the cell, enhancing the dynamic capabilities of code cells 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 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" in Visual Studio Code. The incorrect path causes an error indicating that the terminal process could not be started because the executable shell file path 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 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 as a question mark when copied into Visual Studio Code (VS Code) on Fedora 39. The problem persists even when all extensions are disabled, and the character displays correctly in other applications like Firefox, indicating a potential 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: 202
Summarized Issues:
- Visual Studio Code Debugging Issues: Users have reported various issues with debugging in Visual Studio Code, including problems with the debug toolbar becoming inaccessible on macOS, and the "Publish Branch" feature failing when using a SOCKS5 proxy. These issues hinder the debugging process and require workarounds or fixes to restore functionality.
- Visual Studio Code Extension and Marketplace Issues: Several issues have been identified with extensions and the marketplace in Visual Studio Code, such as difficulties downloading extensions, invalid extensions being removed, and the GitHub Copilot extension causing terminal input issues. These problems affect the usability and reliability of extensions, impacting user workflows.
- Visual Studio Code Performance and Usability Problems: Users have experienced performance issues in Visual Studio Code, including high CPU usage, slow operations, and problems with the redo functionality. These issues degrade the user experience and may require downgrading to previous versions for stability.
- Visual Studio Code Configuration and Environment Issues: Problems with configuration and environment settings in Visual Studio Code have been reported, such as terminal profiles not being recognized, and environment variables not resolving correctly. These issues complicate the setup and use of the development environment.
- Visual Studio Code Feature Requests: Users have requested new features for Visual Studio Code, including the ability to control the casing of Activity Bar titles, and enhancements to the search functionality. These requests aim to improve customization and efficiency in the development workflow.
- Visual Studio Code Git and Source Control Issues: Issues with Git and source control in Visual Studio Code have been reported, such as git filters not applying correctly and problems with the Source Control Management view. These issues affect version control operations and require attention to ensure smooth collaboration.
- Visual Studio Code User Interface and Accessibility Issues: Users have encountered issues with the user interface and accessibility in Visual Studio Code, including problems with the Activity Bar, hover positioning, and text rendering. These issues impact the visual consistency and accessibility of the editor.
- Visual Studio Code Terminal and Shell Issues: Problems with the terminal and shell integration in Visual Studio Code have been reported, such as the terminal not responding to abort signals and issues with the integrated suggestion feature. These issues affect the functionality and reliability of the terminal.
- Visual Studio Code Language and Syntax Issues: Users have reported issues with language and syntax support in Visual Studio Code, including problems with CSS property suggestions and Python operator replacements. These issues affect code editing and require fixes to ensure accurate syntax highlighting and language support.
- Visual Studio Code Remote Development Issues: Issues with remote development in Visual Studio Code have been identified, such as problems with SSH connections and the VS Code Server not recognizing custom environment variables. These issues hinder remote development workflows and require solutions to ensure connectivity and compatibility.
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: 170
Summarized Issues:
- Screen Reader Issues: Visual Studio Code has encountered problems with screen readers, particularly NVDA and JAWS. NVDA repeats the penultimate line when the last line is empty, while JAWS does not deactivate its virtual cursor during search operations, causing unintended shortcuts.
- Extension and Feature Installation Issues: Users have reported unexpected installations and feature recommendations in Visual Studio Code. The JS Debugger Companion installs without user consent, and the AI Toolkit is suggested when Ollama is detected, causing confusion.
- Performance and Resource Usage Problems: Visual Studio Code users experience performance slowdowns and high resource usage. Issues arise from multiple instances with the "(Github) Output" tab and pasting text in the Source Control panel, leading to delays and high CPU usage.
- Terminal and Input Responsiveness Issues: Problems with terminal responsiveness have been reported in Visual Studio Code. The integrated terminal becomes unresponsive after ALT key interactions, and the "W" key malfunctions, affecting typing.
- Walkthrough and Guide Access Issues: Users face difficulties accessing walkthrough guides in Visual Studio Code. Commands intended to open specific guides instead display the 'Welcome' page, indicating missing category IDs.
- Copilot and Chat Feature Issues: Visual Studio Code's Copilot and chat features have several bugs. Copilot posts edits to prompts instead of code, and chat variables are difficult to search, disrupting user workflow.
- Login and Authentication Problems: Users encounter login issues in Visual Studio Code, particularly with Azure and Microsoft accounts. Problems include server-side errors and frequent logouts, affecting user access.
- File and Explorer Issues: Visual Studio Code users report problems with file access and explorer functionality. Issues include inability to open the file explorer and missing folder names in the explorer view.
- Remote Development and SSH Issues: Problems with remote development and SSH connections are reported in Visual Studio Code. Users face errors due to outdated libraries and prerequisites not being met on remote hosts.
- Settings and Configuration Issues: Visual Studio Code users experience issues with settings and configurations. Problems include unresolved variables in
tasks.jsonandlaunch.json, and incorrect settings application.
- Update and Installation Issues: Users report problems with updating and installing Visual Studio Code. Errors include "Access is denied" during updates and incorrect installations of extensions.
- Memory and Resource Management Issues: Visual Studio Code has memory leak problems, particularly with disposable objects not being properly managed, leading to resource leaks and performance degradation.
- Chat and Agent Mode Issues: Users face issues with chat and agent modes in Visual Studio Code. Problems include chat UI deadlocks and agent mode limitations, affecting user interaction and functionality.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
- Toxicity Score: 0.55 (Aggressive initial comment, Caps lock usage, Potential for misunderstanding.)
- This GitHub conversation involves a user expressing frustration with a recent update, which they claim has removed essential functionality, threatening to switch to competing products if not resolved. Another user responds by suggesting the issue might be related to an extension and advises against using all caps, which is perceived as yelling. The tone is tense, with the initial comment being particularly aggressive, while the response attempts to de-escalate the situation by providing a potential solution and a reminder of netiquette.
-
your layout is fucking now I can'y fine file explorer ,
- Toxicity Score: 0.65 (Strong language, dismissive response, initial aggression.)
- This GitHub conversation involves a user, heangchihav, expressing frustration with strong language about a layout issue, which triggers a response from another user suggesting the use of Google Translate due to the unclear language. The tone is initially aggressive and dismissive, but a third user provides a calm, constructive suggestion to resolve the issue.
-
Increase maximum problems per file (or allow customization)
- Toxicity Score: 0.75 (Aggressive language, Frustration with automated response, Demand for human review.)
- This GitHub conversation involves a user, Mike Nelson, expressing frustration and dissatisfaction with the automated closure of their feature request by the vs-code-engineering bot. The tone of the conversation is tense, with Mike Nelson using aggressive language and demanding human intervention in the review process. The trigger of tension is the bot's action of closing the issue as a duplicate without a manual review, which Mike Nelson perceives as dismissive of their efforts.
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: 16
Key Open Pull Requests
1. title: This pull request involves a series of updates and improvements to the Visual Studio Code project, including the addition of inline edit tests, fixes for missing TypeScript scopes, enhancements to the chat prompt decoder, and various refactoring efforts to improve code structure and functionality, as well as addressing issues related to chat history storage, markdown conversion, and semantic token handling.
- URL: pull/246391
- Merged: No
- Associated Commits: 324d1, 1a602, 0bc67, 760b9, 39b68, 67524, 297f8, f0bb1, 75cea, 7a92a, 61e22, 3452c, ab9b3, 5b2b8, 4741f, 87111, 78c2b, fe3f4, 440da, 350e5, 721cf, 0160d, 4e151, 1450f, 11041, 574f9, 434c0, 968a8, 5f2ba, c6141, 0ab41, 63451, 32f9c, 8757e, d5487, 9d521, b2a09, 027e5, 8c60b, a32a3, 90034, 22d02, 02e46, c21a8, 2ad2a, f4a15, 6d74a, 769ab, f69cf, 96dea, 820a6, d0b11, 58c1e, c593e, 86489, fc836, a5431, 9125a, b0abf, 810f3, 8363e, 0d243, 4a18b, 00844, 8d1d5, dc88a, e1c53, 46c46, fd149, 0bd8e, 58d6d, ca5cb, a5501, 34d2b, 681fb, e9517, cee65, 7700c, e275f, 84c46, 599b9, b8965, 111ae, 032c7, d83e7, e87de, d2458, e8ab1, 4095b, f6b2d, fef48, cd3ae, 821b2, 63b5c, 1c1bd, b3a3f, 85492, d2a63, 77d9e, 472a7, c231d, 3d639, a9af8, 2b548, 0023c, 1fec1, 42f6f, 64126, bb2b0, d9156, 8ecef, 174af, 56ebf, 57dfc, 5df37, c6a20, 3a0b7, 75585, fa33e, 5d194, 3d39b, 6916a, e2afb, b952f, 2a049, 33c84, c9a61, 1afdf, e2947, 1e23a, 76ce3, 9d0bf, 88b8f, 0998f, 7021e, b4e68, 459f9, 613e2, 8e38e, 7dbf2, 40a7e, 060f2, 74ff8, 7ec68, b2060, d7523, b237e, 165c1, bb1d9, f074f, 65449, 807a4, 99732, 0c8f5, 3c7a7, 9c6b2, 91274, 66392, 2138f, d15f6, 4a0e9, ddede, 7ffe4, 91933, 71607, 76458, 933f9, 9ad84, 9143f, 41263, 25f25, f0ee5, 77a0b, 6c7a4, 41ecd, 0a94f, acf8d, ed478, 47932, 7b2ea, 0b0be, a19a7, 67562, e6348, 7aecf, c778b, 38c0e, 3a720, 6eddc, 8a1f5, 34c0c, 2fc67, 08ae9, 6a9a1, f2718, b17a4, 043f6, 49437, 36397, 0ab62, 18afe, 88c1f, f443e, bdc1a, 22141, a4a4b, a82ba, 385ab, 3ae3b, f093f, fd7fa, fe9ef, be37d, ae5d9, 07e01, 3f512, 1b1ed, febbc, 48cb4, 4293d, 816da, c3b0f, 522b9, f5bce, 0bb72, 296e7, 0440f, 84908, 03dc8, 88b8c, bb50f, 8e629, da19d, 8e86c, 05541, bf209, 63987, 0182d, c3806, f8308, 0ee4f, 609b6, 0a5f0, 11d22, 57008, d107c, 0f2f8, 550fe, 9cc0f, 92439
2. Scope down shell env api : This pull request aims to refine the shell environment API by scoping down its functionality across various shells such as zsh, bash, fish, and pwsh, addressing issues #245695 and #244140 in the Visual Studio Code repository.
- URL: pull/245899
- Merged: No
3. separate prompt and instructions files: This pull request aims to separate prompt and instructions files in the Visual Studio Code project, involving multiple commits that update various components and files related to prompts, with contributions from Oleg Solomko.
- URL: pull/246231
- Merged: No
Other Open Pull Requests
- New Features in Visual Studio Code: This set of pull requests introduces new features to the Visual Studio Code project, enhancing its functionality and user experience. The features include middle mouse button scrolling, a new configuration option for editor title scrollbar visibility, and a maximum line display setting for the debug console.
- Bug Fixes and Improvements: These pull requests address various bugs and improvements in the Visual Studio Code project, such as fixing semantic inconsistencies in the Git extension, correcting a typo and type mismatch, and resolving issues with TypeScript expression coloring and MIME type selection.
- Dependency Updates and Code Refactoring: This pull request involves updating dependencies like 'tokio' and 'crossbeam-channel' and proposes changes to remove working set attachment logic for agent mode, which includes a fix for a mock service.
- Enhancements for Notebook and Debugging: These pull requests introduce enhancements for notebook handling and debugging in Visual Studio Code, such as allowing extensions to provide a
NotebookMapperand triggering actions on notebook cell containers.
- Open Suggestions and Feedback Requests: These pull requests propose suggestions and seek feedback on various aspects of the Visual Studio Code project, including the
IEnvironmentServiceand the mode picker in the quick chat feature.
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: 175
Key Closed Pull Requests
1. Add Dashboard button next to open aux bar button: This pull request proposes adding a Dashboard button next to the open auxiliary bar button in the Visual Studio Code interface, as indicated by the title, although it was not merged into the main codebase.
- URL: pull/246004
- Merged: No
- Associated Commits: c5343, b8ad5, d773f, 09abb, 2b0a6, 5d527, b25ca, 2fe66, 2c9ca, d0b07, b3f2d, d9248, 610b9, d4f25, ba0d9, 18ebc, c09c9, 4a23d, 7cd29, 087f2, b8fdd, aabfb, e77d9, a3296, 1bd2f, 53a25, e84c0, f137b, d54d3, 6eece, 1deb3, b10b3, b118a, 4239f, 51b2e, 07c6c, 05ffc, c4f53, cd5bd, a8cc9, 716b7, f6174, 52dbd, 3660c, 0e1bb, 23ce7, 66533, e51f6, 66e9f, fd3bd, 0bd83, 9f4b7, 5385a, a644d, b4d78, 1b2b6, 9ed68, 89f71, 3d319, 9dc36, 24837, 65cb7, 1b9e2, 35d45, 17cb4, 15c5d, da405, f1876, 857f1, 53f6a, 2e78d, e1237, b70de, ef272, 04550, 2c740, 74538, c27d9, cd00a, cb21c, 9639f, aee7f, f9436, a7a99, 2a8b3, 1ccb1, 0db00, 95ef4, bcaf1
2. Engineering - 🆙 bump deemon: This pull request involves a series of updates and improvements to the build and deployment scripts for the Visual Studio Code project, including tasks such as speeding up compilation, improving logging, fixing pipeline conditions, and adjusting the script for better error handling and environment variable management, although it was ultimately not merged.
- URL: pull/246055
- Merged: No
- Associated Commits: f678e, 097ca, f8d23, 12344, c9bc9, fb87d, ead3a, 84eb6, 0a466, 04667, ab061, e7b86, aaf15, bdbb2, fc63d, 875d1, bef3f, 237f8, f006e, 62bf4, 044df, 20007, f5566, 68b27, 269df, 726d9, 97bf9, 173a2, 13946, a2aca, 2f9fb, 3aa1d, 21f7e, bf327
3. Engineering - refactor macOS stage: This pull request involves a comprehensive refactoring of the macOS stage in the Visual Studio Code project, focusing on optimizing the build process by folding sign steps into jobs, speeding up compilation, improving scripts and logging, handling errors, and making various adjustments to tasks and conditions to enhance the overall efficiency and reliability of the macOS build pipeline.
- URL: pull/246059
- Merged: 2025-04-09T11:22:35Z
- Associated Commits: aa463, 610f8, 245a2, 95b60, 5fe78, 98510, b904d, c5fcb, 31e14, d7041, 366b6, 488e3, ea4be, 49edf, d0d92, a1777, e525c, 390b2, 6b8d3, 7b04a, 00a44, ecd3a, 23124, 23d8f, 8c32a, f6e52, e9636, 4adea, 7802b
Other Closed Pull Requests
- Linux Code Signing Enhancements: This topic covers the implementation of parallel execution and background processes for Linux code signing tasks in the Visual Studio Code project. The pull requests detail the setup, debugging, and improvement of scripts to achieve these functionalities, enhancing the efficiency of the code signing process.
- Prompt File Enhancements: Several pull requests introduce new syntax support and features for reusable prompt files in the Visual Studio Code project. These include support for
${variable},@mention,/commandsyntax, and a "run prompt" editor action button, enhancing the functionality and user interface of prompt templates.
- Front Matter and Markdown Enhancements: This topic includes improvements to markdown and Front Matter header functionalities in the Visual Studio Code project. The pull requests introduce a markdown "extensions" decoder, Front Matter header syntax support, and in-editor decorations, along with refactoring and unit test enhancements.
- Chat and Editor Enhancements: Enhancements to chat input functionality and editor features are covered in these pull requests. They include rendering attachments in prompts, enabling drag and drop of notebook outputs into chat, and introducing a diff hunk toolbar for markdown cells in preview mode.
- Prompt Language and Execution: These pull requests focus on the introduction and execution of a new "prompt" language in the Visual Studio Code project. They include changes to condition prompt language features, execution of untitled prompt documents in chat, and the introduction of a "prompt-basics" language extension.
- Miscellaneous Enhancements: Various other enhancements are covered, including image alt text generation, a custom tracing service, and improvements to auxiliary window options. These pull requests address specific issues and enhance the overall functionality and user experience of the Visual Studio Code project.
- Bug Fixes and Refactoring: This topic includes pull requests that address specific bugs and refactor existing code. They cover issues such as navigating to the definition of built-in DOM classes, handling prompts as attachments, and reapplying background codesign changes for Windows.
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.
- change editing mode back if chat was the one that changed it
- Toxicity Score: 0.55 (Defensive responses, escalating tension, impatience)
- This GitHub conversation involves username1 and username2, where username1 expresses frustration over a perceived oversight by username2, leading to a tense exchange. Username2 responds defensively, which escalates the tension. The tone shifts from collaborative to confrontational, with both parties showing signs of impatience.
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 | 229 | 22 | 43 | 83 |
| roblourens | 200 | 25 | 18 | 88 |
| lszomoru | 247 | 19 | 8 | 43 |
| meganrogge | 146 | 0 | 27 | 99 |
| connor4312 | 113 | 6 | 29 | 108 |
| legomushroom | 216 | 19 | 3 | 11 |
| jrieken | 106 | 13 | 17 | 57 |
| sandy081 | 54 | 8 | 9 | 62 |
| i-stefan-1994 | 0 | 0 | 131 | 0 |
| TylerLeonhardt | 30 | 4 | 12 | 84 |
Access Last Week's Newsletter: