Weekly GitHub Report for Kubernetes: August 11, 2025 - August 18, 2025 (12:04:46)

Weekly GitHub Report for Kubernetes

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
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v1.32.3

1.2 Version Information:

The Kubernetes 1.32 release, announced on March 11, 2025, introduces several key updates and improvements detailed in the official CHANGELOG, with additional binary downloads available. This version continues to enhance Kubernetes' functionality and stability, reflecting ongoing development trends in the platform.

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.

1. Deprecations are not marked correctly: This issue addresses the problem that deprecations in the client-go codebase are not consistently marked according to Go conventions, causing tools like staticcheck and IntelliJ to fail in detecting deprecated code usage. The reporter highlights specific examples of correct and incorrect deprecation comments and suggests that adding linting to enforce proper deprecation formatting would help consumers migrate away from deprecated code more effectively.

   • The comments discuss the complexity of reliably linting deprecation comments due to variations and false positives, with consensus that a standard linter upstream (e.g., in golangci-lint) would be ideal rather than a Kubernetes-specific one. Participants agree on the importance of fixing existing incorrect deprecations and mention ongoing efforts to identify and correct them, while acknowledging limitations in tooling and the need for practical short-term fixes.
   • Number of comments this week: 10

2. Move SELinux CI jobs to RHEL9: This issue requests updating several SELinux end-to-end test jobs to run on RHEL9 instead of RHEL8, as RHEL8 is outdated and lacks support for containerd 2.x. The problem involves SELinux context denials preventing containerd and runc from starting containers properly on RHEL9, requiring investigation and temporary workarounds such as relabeling binaries or downgrading jobs back to RHEL8.

   • The comments detail attempts to move SELinux CI jobs to RHEL9, revealing SELinux denials caused by incorrect file labels on containerd and runc binaries. Investigations showed differences in container-selinux package installation between RHEL8 and RHEL9 images affecting binary labeling, leading to intermittent test failures on AWS and GCE. Temporary downgrades to RHEL8 and ongoing updates to test jobs were discussed to address these issues.
   • Number of comments this week: 7

3. Priority for static Pods: This issue requests an official and documented method to assign a non-zero priority to static Pods in Kubernetes, addressing the current limitation where static Pods cannot reference API objects and are rejected if they specify .spec.priority. The discussion highlights the need for distinguishing critical static Pods by priority to control startup and shutdown order, while considering the constraints imposed by the kubelet and admission controllers, and suggests potential solutions such as exempting mirror Pods from certain admission checks and documenting supported priority classes.

   • The comments clarify that static Pods do not currently support priorityClassName because they run without the API server, and while spec.priorityClassName is ineffective, spec.priority is used by the kubelet for ordering and criticality decisions. Participants discuss the implications of priority on eviction and shutdown order, propose documenting the limited support for built-in priority classes, and suggest exempting mirror Pods from admission controller checks to allow setting priorities, with a consensus toward improving documentation and possibly expanding support for certain priority ranges in static Pods.
   • Number of comments this week: 7

4. [Failing test] E2E tests for Dynamic Resource Allocation beta features against a Kubernetes master cluster created with sigs.k8s.io/kind with kubelet from the "current - 1" release: This issue concerns failing end-to-end tests for Dynamic Resource Allocation beta features when run against a Kubernetes master cluster created with kind, specifically using the kubelet from the "current - 1" release. The failure occurs during the preparation phase because the test infrastructure attempts to download a non-existent Kubernetes release file, causing the test setup to break.

   • The comments discuss the root cause being a version skew issue where the master branch is ahead of the latest stable release, leading to missing release files. Contributors suggest workarounds such as adjusting the version skew logic or using alternative release URLs, with one approach successfully tested in a related job, indicating a path forward to resolve the problem.
   • Number of comments this week: 6

5. deployDevicePlugin leaks the extended resource in node's status.Allocatable/Capacity: This issue reports that the deployDevicePlugin function improperly retains the extended resource example.com/resource in a node's status Allocatable and Capacity fields after test completion, leading to conflicts when multiple tests use the same extended resource within a cluster. The expected behavior is for deployDevicePlugin to clean up this resource from the node's status once the device plugin deployment test finishes, preventing resource leakage.

   • The comments include tagging relevant teams and individuals, confirming the issue's acceptance and priority, and assigning the issue to the original reporter for resolution.
   • Number of comments this week: 5

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.

1. apimachinery's unstructured converter panics if the destination struct contains private fields: This issue describes a panic occurring in the apimachinery's DefaultUnstructuredConverter when it attempts to convert an unstructured object into a destination struct that contains private (non-exported) fields. The reporter expects the converter to safely ignore these private fields instead of panicking, as this problem arises particularly with protobuf-generated gRPC structs that include private fields for internal state management.
2. Integration tests for kubelet image credential provider: This issue discusses the possibility of adding integration tests specifically for the kubelet image credential provider, similar to the existing tests for client-go credential plugins. It suggests that since there are already integration tests for pod certificate functionality, implementing comparable tests for the kubelet credential plugins would be a logical and beneficial extension.
3. conversion-gen generates code that leads to panics when fields are accessed after conversion: This issue describes a bug in the conversion-gen tool where it generates incorrect conversion code for structs that have changed field types between API versions, specifically causing panics when accessing fields like ExclusiveMaximum after conversion. The problem arises because the generated code uses unsafe pointer conversions instead of properly calling the appropriate conversion functions, leading to runtime errors when the converted fields are accessed.
4. Failure cluster [ff7a6495...] TestProgressNotify fails when etcd in k/k upgraded to 3.6.2: This issue reports a failure in the TestProgressNotify test that occurs when the etcd component in the Kubernetes project is upgraded to version 3.6.2. The test times out after 30 seconds waiting on a result channel, with multiple errors indicating that the embedded etcd server fails to set up serving due to closed network connections and server shutdowns.
5. RBAC Permissions for HTTPRoute to Built-in admin ClusterRole: This issue proposes adding explicit RBAC permissions for HTTPRoute resources from the Gateway API to the built-in admin ClusterRole, enabling users with this role to manage these resources without requiring custom RBAC configurations. This change aims to align the admin role with the evolving Kubernetes networking standards by supporting the Gateway API—positioned as the successor to the deprecated Ingress API—thereby reducing administrative overhead and improving usability while maintaining security through namespace-scoped access.

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: 35

Summarized Issues:

• Test Failures and Flakiness in Kubernetes Components: Multiple issues report flaky or failing tests across various Kubernetes components, including PSI stats summary, Kubelet config merging, scheduler metrics, pod crashloop behavior, resource allocation, API machinery discovery, and device class scheduling. These failures often stem from race conditions, resource leaks, mismatches in expected states, or external dependencies like missing release files, causing intermittent or persistent test instability.
• issues/133456, issues/133457, issues/133464, issues/133472, issues/133488, issues/133493, issues/133494, issues/133495, issues/133531, issues/133563

• Scheduler and Pod Scheduling Issues: Several issues highlight problems with pod scheduling, including incorrect handling of pod-deletion-cost annotations, imbalanced pod distribution during rolling updates, negative GatedPods metrics, and scheduling delays due to device class updates. These issues cause resource underutilization, imbalanced workloads, and pods remaining unschedulable or incorrectly accounted for in metrics.
• issues/133464, issues/133529, issues/133531

• Resource Management and Allocation Problems: Issues report resource leaks such as extended resources not cleaned up after tests, flaky failures due to resource claim mismatches, and requests for improved event emission on pod resize operations. These problems lead to resource conflicts, scheduling inconsistencies, and lack of visibility into resource allocation states.
• issues/133488, issues/133493, issues/133528

• EndpointSlice and DNS Resolution Failures: One issue describes frequent churn and endpoint count exceeding defaults in EndpointSlice objects causing temporary DNS resolution failures (NXDOMAIN) in coredns for healthy VMs, likely due to delayed and inconsistent EndpointSlice updates under control-plane load. This results in intermittent DNS failures impacting cluster stability.
• issues/133474

• Feature Gate and API Stability Enhancements: There are proposals to codify explicit dependencies between feature gates to enforce prerequisite maturity levels and to clean up post-GA code for InPlacePodVerticalScaling, including removing feature gates and handling version skew. These efforts aim to improve feature lifecycle management and API stability.
• issues/133533, issues/133537

• InPlacePodVerticalScaling (IPPR) Feature Issues: Several issues address IPPR feature problems, including JSON marshaling errors during resource allocation, lack of support for memory request changes affecting cgroup values, and cleanup tasks after GA. These highlight ongoing challenges in resource scaling and management within this feature.
• issues/133538, issues/133539, issues/133537

• Code Quality and Refactoring Requests: Issues request refactoring of Windows kube-proxy syncProxyRules to reduce complexity and improve maintainability, and address incorrect deprecation markings in client-go causing tooling failures. These focus on improving code readability, maintainability, and tooling support.
• issues/133502, issues/133566

• API and Client Library Improvements: Requests to update the newReflectorWithOptions function to support ListerWatcherWithContext instead of ListerWatcher aim to unblock kube-state-metrics migration and avoid breaking public APIs. This reflects ongoing efforts to modernize client libraries and improve API ergonomics.
• issues/133542, issues/133567

• Cluster and Component Startup Failures: Issues report panics and startup failures such as kube-controller-manager, kube-apiserver, or kube-scheduler crashing on invalid log-flush-frequency values, and kubemark hollowProxy failing due to uninitialized HealthServer, preventing proper component launches. These bugs cause critical cluster component instability.
• issues/133520, issues/133526

• Security and Compatibility Updates: An issue requests updating SELinux end-to-end CI jobs to run on RHEL9 to address compatibility problems with containerd 2.x and SELinux labeling, improving container runtime initialization on cloud environments. This update is necessary to maintain CI reliability and security compliance.
• issues/133484

• Static Pod Priority and Scheduling Limitations: There is a request for an official method to assign non-zero priority values to static Pods, addressing current limitations that prevent static Pods from referencing API objects for priority, which causes admission rejections and limits control over scheduling and shutdown order.
• issues/133535

• Service Multi-Protocol Port Configuration Anomalies: An issue highlights inconsistencies in Kubernetes Service multi-protocol port configurations where patch operations fail to maintain shared nodePort states, causing only the first port to be effective and requiring multiple patches to resolve. This leads to unexpected behavior in service port management.
• issues/133564

• IPVS Mode Maintenance Uncertainty: An issue points out outdated internal documentation about the IPVS mode of kube-proxy, noting that IPVS is neither actively maintained nor officially deprecated, and calls for a clear decision on its future to clarify maintenance and support status.
• issues/133536

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: 6

Summarized Issues:

• Security Vulnerabilities and Mitigations: Several issues address security vulnerabilities in Kubernetes components, including a critical flaw in the NodeRestriction admission controller that allows node users to delete their own node objects by patching with an OwnerReference, and a dependency upgrade needed to fix CVE-2025-27144. Another issue confirms that CVE-2025-47907 does not impact Kubernetes due to lack of affected method usage and recent Go version updates effectively resolving it.
• issues/133471, issues/133478, issues/133561

• Test Failures in Node Services Startup: There is a reported failure in the end-to-end node test related to starting internal node services during the SynchronizedBeforeSuite phase, specifically affecting containerd and CRI-O runtimes in the 1.34 release informing jobs. The failure occurs because the start command for the server "services" exits with status 255, causing the test to fail.
• issues/133460

• Audit Logging Configuration Issues: An issue highlights the inability to enable audit logging on Kubernetes clusters created with kubeadm, where applying audit settings causes the kube-apiserver to fail restarting and the audit configuration is not applied. This problem is accompanied by PodSecurity warnings and errors related to mirror pod creation.
• issues/133574

• Community-Driven MCP Server for Kubernetes: A free MCP server for Kubernetes has been created and shared by Corey A. (Hawaiideveloper) to learn from and resolve common issues using official Kubernetes documentation and community-reported problems. The project requests community support and QA testing to improve the server.
• issues/133453

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: 42

Key Open Pull Requests

1. e2e: node: cpumanager: replace the test suite: This pull request replaces the old cpumanager end-to-end test suite with a new, more comprehensive suite that has been rewritten and validated through the full 1.34 release cycle, thereby improving test coverage and cleaning up related utilities and obsolete tests.

• URL: pull/133463

• Merged: No

• Associated Commits: 2b229, cea6f, 9ccf0, 23fff, 8f232, 9d9f8, 2cf92, 0a9e3, 75452, aff5a, 858a3, 092df, 19dea

2. fix many incorrect deprecation warnings in godoc: This pull request fixes numerous incorrect deprecation warnings in the Go documentation by ensuring that API deprecations are properly formatted and parsed as deprecations, improving their visibility in godoc (pkgsite), developer tools, and linters.

• URL: pull/133571

• Merged: No

• Associated Commits: 8c139, 30f4f, 9fabc, 1dd42, fa579, 80071, 668b3, 2b47e, db5dd, 189d6

3. e2e: node: cpumanager: cleanup and tidification before test replacement: This pull request performs a final cleanup and reorganization of utilities and shared code in the cpumanager end-to-end node tests to prepare for replacing the old tests with rewritten ones, aiming to minimize logic changes and improve code tidiness before the major test replacement.

• URL: pull/133462

• Merged: No

• Associated Commits: 1a4e2, bb7cf, 30ca6, d86d7, af53d, e839a, 8612c

Other Open Pull Requests

• Performance optimization in ResourceDescriber: This pull request fixes a performance bug by modifying the ResourceDescriber to avoid redundant network requests for the main resource when it is already available from the parent. This eliminates an N+1 query issue and significantly speeds up resource description operations, especially during prefix searches.
• pull/133498

• Hashing algorithm migration and lint enforcement: This change eliminates the use of the MD5 hashing algorithm across the Kubernetes project by blocking any new MD5 usage with a lint rule and migrating existing non-cryptographic MD5 uses to the faster and non-obsolete FNV-1a algorithm. Storage-related tests that require cryptographic hashing are switched to SHA-256 to maintain security.
• pull/133511

• Configuration validation for log-flush-frequency: This pull request adds validation to ensure that the log-flush-frequency configuration parameter is strictly positive, preventing invalid zero or negative values that previously caused system panics. Instead of panicking, the system now returns an error for invalid values.
• pull/133540

• PodFailurePolicyOnPodConditionsPattern Status field omission: This feature allows the Status field in PodFailurePolicyOnPodConditionsPattern to be omitted, addressing errors in the Python Kubernetes client caused by the Status not being explicitly set to "True". The kube-apiserver automatically sets this downstream, so explicit setting is no longer required.
• pull/133479

• Cache and handlers channel optimization: This pull request improves cache and handlers code by eliminating unnecessary channel allocations and replacing them with nil channels to avoid blocking goroutines. This resolves issues with testing/synctest that arise when channels are created outside its control.
• pull/133500

• Workqueue shutdown and metrics goroutine cleanup: The workqueue shutdown process is improved by ensuring that the metrics-related goroutine is properly cleaned up before ShutdownWithDrain returns. This enables tests using workqueues with metrics to reliably pass goleak checks and prevents flaking in CI.
• pull/133524

• Base image updates for node-perf and volume/rbd components: The base image for the node-perf/nbp-eb component is updated from stretch-slim to trixie-slim to improve the environment and partially address issue #131874. Similarly, the volume/rbd base image in the test folder is updated for cleanup and maintenance related to the same issue.
• pull/133458, pull/133489

• Sample-controller registration cleanup: This pull request removes outdated code in the sample-controller registration to improve code maintainability and address issue #131747.
• pull/133459

• kubectl drain command stale Pod info fix: This fix ensures that the latest Pod data is re-fetched during eviction retries in the kubectl drain command, preventing errors caused by using stale Pod information.
• pull/133461

• Static pods termination priority on node shutdown: This bug fix ensures static pods are terminated last during node shutdown by assigning them the highest priority for deletion. Previously, static pods lacked local priority values and were not deleted in the intended order.
• pull/133465

• API group validation error message improvement: The API group validation logic in APIEnablementOptions.Validate is refactored to produce more descriptive error messages including group versions for unknown API groups. Unit tests are updated to reflect these enhanced error messages.
• pull/133466

• CPU limit added to cpu-stress-pod in PSI tests: A CPU limit of 500m is added to the cpu-stress-pod to generate CPU pressure more reliably, especially on nodes with abundant CPU resources.
• pull/133473

• Structured logging in pkg/credentialprovider: This pull request migrates the pkg/credentialprovider package to use structured logging by adding metadata to improve clarity and debuggability of image pull error messages. This facilitates easier correlation of errors with specific plugins or images.
• pull/133475

• Retries and simplification in node crictl test: The node's crictl test is improved by adding retries, calling the binary with its absolute path, and checking both stderr and stdout for expected output. The test is simplified to rely solely on the crictl version command output to improve reliability.
• pull/133476

• Node e2e test image pull policy bug fix: This fix allows the IfNotPresent image pull policy to be used in node end-to-end tests instead of incorrectly overriding it to PullNever when the policy is not PullAlways.
• pull/133477

• Volume mount uncertainty handling improvement: This bug fix marks a volume mount as uncertain before setup if the setup process takes too long, improving handling of delayed volume mounts in Kubernetes.
• pull/133481

• Removal of automaxprocs workarounds: This pull request removes automaxprocs workarounds in favor of the built-in container-aware GOMAXPROCS support introduced in Go 1.25, simplifying and modernizing resource management once the project upgrades to Go 1.25.
• pull/133492

• Integration test environment variable adjustment: Integration tests are modified by setting KUBE_PANIC_WATCH_DECODE_ERROR to false to prevent server panics on watch decode errors caused by intentionally inserted undecodable data. This allows tests to continue validating edge cases without process termination.
• pull/133503

• Testing Kubernetes with etcd built images: This feature introduces testing of Kubernetes using etcd built images to validate their integration and functionality within the project.
• pull/133504

• Use of Go 1.22 generic reflect.TypeFor: The code is refactored to use the Go 1.22 generic function reflect.TypeFor instead of reflect.TypeOf, improving type safety, eliminating dummy values, reducing allocations, and making the code cleaner for generic programming.
• pull/133508

• VAP e2e test race condition fix: This pull request fixes a flake race condition in the VAP end-to-end test by adding a known example API group suffix to prevent the race, addressing issue #133505.
• pull/133509

• PVC resizing error message correction: The error message related to Persistent Volume Claim resizing is improved by correcting the misleading message that implied only dynamically provisioned PVCs could be resized.
• pull/133510

• kubeadm timeoutForControlPlane conversion fix: This bug fix adds the missing conversion for the timeoutForControlPlane parameter in kubeadm.k8s.io/v1beta3.ClusterConfiguration, ensuring the specified timeout is honored during kubeadm init instead of defaulting to 4 minutes.
• pull/133513

• Scheduling optimization skipping PreEnqueue plugins: Scheduling behavior is modified to skip running PreEnqueue plugins when a pod is activated from the backoff queue, avoiding redundant checks previously performed upon moving the pod to the active queue.
• pull/133518

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: 19

Key Closed Pull Requests

1. Clarify staging repository READMEs: This pull request clarifies in the staging repository README files that these repositories are not intended for direct contributions, redirects contributors to the appropriate main Kubernetes repository for submitting pull requests, and provides additional documentation and links to guide users on the correct contribution process.

• URL: pull/133570

• Merged: Yes

• Associated Commits: 7c43e, 011d5, 8919a, ada2e, e49f6

2. Fix crashloopbackoff #133472: This pull request addresses a bug in Kubernetes kubelet by ensuring that the CrashLoopBackOff backoff logic is applied immediately after a container's first crash, preventing unnecessary restart attempts without delay and aligning pod lifecycle behavior with expected standards.

• URL: pull/133483

• Merged: No

• Associated Commits: 6e004, e898e

3. fix/update test httpd base image: This pull request aims to update the test/httpd base image to a newer Alpine version to ensure the testing environment uses an up-to-date and consistent image.

• URL: pull/133487

• Merged: No

• Associated Commits: 61a1c, 8f481

Other Closed Pull Requests

• NodeRestriction admission controller security fixes: Multiple pull requests update the NodeRestriction admission controller to fix a security vulnerability by preventing nodes from modifying their OwnerReferences. This change stops nodes from deleting their own node objects through malicious patching, enhancing cluster security.
• [pull/133467, pull/133468, pull/133469, pull/133470]

• Dependency and environment version bumps: Several pull requests update Kubernetes dependencies, container images, and versions to use Go 1.23.12 or 1.24.6 along with distroless iptables. These updates ensure the build environment remains current and secure across the project.
• [pull/133516, pull/133517, pull/133521, pull/133522]

• Dynamic resource allocation (DRA) test fixes and diagnostics: One pull request fixes a flake in the DRA scheduler plugin test by addressing timing issues in claim binding, resulting in stable test runs. Another pull request attempts to reproduce flakiness in DRA tests following recent changes, serving as a diagnostic step rather than a fix.
• [pull/133491, pull/133530]

• Bug fixes related to serviceAccountName and liveness probe events: One pull request fixes a bug where setting serviceAccountName to null incorrectly depended on the deprecated serviceAccount field, allowing proper discarding of serviceAccountName. Another pull request addresses liveness probe failures not logging distinct events by modifying spam key generation to include a hash of the event message, preventing event conflation.
• [pull/133485, pull/133497]

• Test image and tooling updates: A pull request updates the base image for Redis test images to Alpine 3.22 as part of cleanup efforts. Another pull request updates the Go version used for publishing bot rules, also as part of cleanup.
• [pull/133486, pull/133568]

• Library dependency update to remove indirect pkg/errors dependency: One pull request proposes updating the json-patch library to versions v5.9.10 and v4.0.13 to remove the indirect dependency on the pkg/errors package.
• [pull/133482]

• Work-in-progress test for branching upstream: A pull request marked as "DNM" is a work-in-progress test related to branching upstream and was not merged.
• [pull/133490]

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
BenTheElder	30	6	5	124
ffromani	31	3	0	16
liggitt	13	5	0	23
dims	7	1	3	28
ylink-lfs	13	6	1	18
bart0sh	13	5	2	16
stlaz	5	2	1	27
pohly	12	1	9	11
aojea	4	2	2	25
richabanker	7	5	4	17