Find meaningful ways to contribute

This issue consolidates five distinct bug fixes and performance improvements. Key fixes include preventing Matplotlib event listener leaks in the GUI, correctly mapping Lichess game results for resignations and timeouts, addressing clock increment calculation errors, optimizing board replay performance from O(N) to a more efficient approach, and removing deprecated locale usage.

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

This issue proposes propagating QueryFlux query tags to backend engines that support native query tagging, such as Snowflake's QUERY_TAG. This would enhance engine-side attribution, cost tracking, and correlation between QueryFlux and backend observability by ensuring tags are visible in engine-specific UIs and reports.

This issue requires designing a "lawful position mechanism" for a transformer model that currently lacks one, which is preventing the assembly of its Stage 3 trunk. The mechanism must adhere to specific geometric constraints and demonstrate a measurable improvement in ordering tokens within the sequence.

The shell integration for GitHub CLI polls for pull request information every 45 seconds, even for branches that have no associated pull request. This unconditional polling consumes GitHub's GraphQL API rate limit unnecessarily, especially on default branches like 'main'. A secondary issue is that cache timestamps are not reliably stored, hindering future optimizations.

This issue identifies a code duplication in the `shep-daemon` project's Windows advisory handling. The same block of code for generating Windows-specific path advisories is being written twice within the `path_advisories.rs` file. The proposed fix is to extract this duplicated logic into a separate function to improve code tidiness.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

This is an open invitation for users to request new features for the Damru Android web automation framework. The maintainer is eager to develop the project and will implement requested features quickly and free of charge.

YouTube has implemented a change that prevents desktop users from posting GIF comments, resulting in various error messages. This issue appears to be server-side and not related to user installations, browsers, or VPNs. The maintainer is seeking community assistance to identify a solution.

This issue requires the development of a TypeScript service layer for managing limited-time product drops in the StarShop marketplace. It involves implementing functionalities for creating, retrieving, updating, and canceling drops, as well as handling user access control, participation tracking, and time-based operations.

The merge sort workshop's step 4 incorrectly rejects a valid slice endpoint in Python. The test specifically requires an omitted end index for slicing the right half of an array, even though explicitly including `len(array)` produces functionally identical and correct results. This discrepancy causes the provided solution to fail the test.

This issue proposes the creation of a `forkd-jupyter-spawner` Python package to integrate forkd as a per-user kernel backend for JupyterHub. The goal is to leverage forkd's ability to share a pre-warmed SciPy stack across multiple kernels, reducing cold-start times compared to existing spawner options like Docker or Kubernetes. The spawner will interact with the forkd controller via its API for starting, polling, and stopping sandboxes, and will handle state persistence and network port forwarding.

The `grit diff -- <path>` command incorrectly reports no changes for staged-only modifications, even when the plain `grit diff` command correctly identifies them. This behavior leads to inaccurate reporting for agents checking for uncommitted changes and contradicts the expected behavior of narrowing the scope of the diff.

On Android, when a user is signed out and attempts to share an image to the Expensify app, the app either freezes on the sharing page or exhibits a flickering share modal and onboarding modal with errors after signing in. This issue is reproducible in both staging and production environments.

This issue addresses a bug where specific dialogs in Avogadro do not display correctly in right-to-left languages due to forced layout direction on individual widgets. The fix involves removing these forced directions and potentially restructuring layouts to ensure proper mirroring for RTL locales. The goal is to improve internationalization and accessibility.

This issue requests the addition of a 'Document Window' option to the right-click context menu of the TechDraw and Spreadsheet workbenches. This feature would provide a more accessible way for users to dock these windows, similar to how it's implemented for 3D views, addressing a usability gap when these windows are undocked.

This issue highlights two problems in a Python discount calculator workshop. First, it clarifies the distinction between `__init__` and constructor calls regarding return values. Second, it points out that several steps require learners to add missing parameter and return type annotations to methods, which are necessary for passing tests, even though the initial instructions don't explicitly mention them.

This issue requests community help to update the documentation for transform plugins to match the established connector documentation standard. The goal is to improve clarity and accuracy by including comprehensive option tables, detailed descriptions for each option, multi-table semantics, runnable examples, and ensuring English and Chinese versions are synchronized. This rewrite aims to address existing issues like missing multi-table options, outdated information, and undocumented features.

The `EnvCheckPolicies` tool currently passes with an exit code of 0 even when all configured policies are skipped due to environment mismatches. This issue proposes modifying the tool to detect when all policies are skipped and instead return an exit code of 2, along with a descriptive message, to indicate that no checks were actually performed.

This issue requests the creation of a no-account smoke test guide for the synthetic demo panel. The guide should walk first-time contributors through starting the demo, verifying image card appearance, testing various UI interactions like search, filtering, preview, pinning, and auto-select, and checking UI localization. It should also specify what to include in manual check notes, using only synthetic screenshots.

This issue requests the addition of a troubleshooting checklist to the installation guide for custom endpoints. The checklist should help users diagnose and describe issues with their custom endpoint setup before reporting a bug, covering client/plugin versions, endpoint functionality, API format, local engine ports, and necessary information for bug reports while emphasizing privacy.

This issue aims to improve keyboard accessibility for an image preview dialog by ensuring that the Tab and Shift+Tab keys keep focus within the dialog's interactive elements. The goal is to prevent focus from escaping the dialog and to maintain expected behavior for closing the dialog and interacting with its controls.

This issue is a contribution task to supplement unit tests for the AscendStore pooling module in vllm-ascend. The task requires adding tests for six sub-layers of AscendStore, focusing on critical paths and boundary conditions, to improve the existing test coverage which is currently around 50%-70%. Specific areas to be tested include data structures, transfer threads, scheduling, worker logic, connectors, and backend abstractions.

This issue aims to migrate the `VLLM_ASCEND_ENABLE_FLASHCOMM1` environment variable to the AscendConfig system. The primary challenge is that the `enable_sp()` function is called in multiple critical paths, including worker initialization where the `current_vllm_config` context is missing. The task requires fixing this context issue and ensuring FlashComm1 can be enabled via `--additional-config` without regressions in distributed inference, MoE, SP, or FlashComm2 behavior.

This issue is a contribution task to enhance vLLM's multimodal capabilities, specifically focusing on video compression (EVS) on NPUs. The goal is to integrate existing EVS functionality into the vLLM-Ascend plugin to leverage NPU performance, with specific acceptance criteria involving model testing, documentation, and community RFC submission.

This issue addresses unbounded collections (asset/pool whitelists and relayer set) stored in a single instance entry within a smart contract. As these collections grow, they increase transaction costs and risk bricking the contract when the instance storage size limit is reached. The proposed solution involves migrating these collections to per-key persistent entries and potentially capping the set size or using pagination for enumeration.

This issue requests the implementation of missing test cases for `Se3`, `So3`, and `So2` geometry primitives. Specifically, it calls for tests to cover exceptions for invalid inputs, gradient checks for differentiability, TorchScript compatibility (JIT), and proper integration within `nn.Module`.

The Kubernetes API server is initializing duplicate instances of its cache and etcd storage for certain resources like service accounts and events. This duplication wastes resources and can lead to unexpected behavior as storage code assumes singleton instances. The issue proposes adding integration tests to validate the number of storage initializations as a mitigation.