Find meaningful ways to contribute

A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.

The direct message conversation panel currently displays the full text of quoted messages, leading to oversized message bubbles and reduced readability. The desired behavior is to truncate quoted messages to a maximum of two lines with an ellipsis, while still showing the author's name. This change aims to improve the user experience by making long quotes more manageable within the conversation thread.

The README file contains a duplicate "Deploying to Vercel" section, causing redundancy and confusion for readers. The issue requires identifying and merging these two sections into a single, clear instruction set.

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.

The teloxide library incorrectly allows sending animations within a media group, despite the Telegram Bot API specification stating this is not possible. The issue arises from the `InputMedia` enum in teloxide including `Animation` as a valid type for media groups, which is then used in the `send_media_group` function.

This issue requests the translation of the "Installation" documentation page from English to Korean. The task involves copying the existing English MDX file, translating its content into natural Korean, and updating metadata. It's marked as a "good first issue" for new contributors, with clear instructions and prerequisites.

The logo/graphic on the HPE case study section of the Layer5 website is not scaling correctly on mobile viewports, leading to inconsistent layout and potential clipping or overflow. The issue requires adjustments to ensure the graphic proportionally fits within its container while maintaining aspect ratio and proper alignment across various mobile screen sizes.

A user is experiencing reboots on their Xiaomi 2409FPCC4G device running Android 14 after attempting to trigger a hook with DFRoot versions 3.3 and 4.1. The device crashes with SIGSEGV errors in critical system processes like 'init' and 'netd' after the hook is triggered, preventing root access. The user suspects issues with executable memory mapping or SELinux compatibility.

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. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

This issue proposes adding a new set of evaluations to measure whether the FSD skill is correctly triggered for various types of queries. The goal is to establish a baseline for current behavior and track the impact of future description changes on skill invocation, ensuring it triggers when needed and avoids unnecessary activations. The proposal includes defining specific query categories and suggests initial language coverage.

This issue requests adding `aria-label` attributes to all icon-only buttons within the application. This is crucial for accessibility, ensuring screen reader users can understand the purpose of these buttons, aligning with WCAG 2.1 Level A requirements. The task involves auditing specific components and adding descriptive labels to buttons that only contain icons.

This RFC proposes extending CUDA graph support to the Vision Transformer (ViT) encoder in vLLM for multimodal models. Currently, the ViT encoder is processed eagerly, incurring significant overhead from numerous small kernel launches. By capturing the entire ViT forward pass into a CUDA graph, this change aims to eliminate launch costs and improve inference latency and throughput for multimodal LLMs.

This is a long-term "help wanted" meta-issue inviting both human contributors and AI agents to scan the repository for bugs, security vulnerabilities, and documentation gaps. Participants are encouraged to submit Pull Requests (PRs) for identified issues, with merged PRs being credited in the changelog and release notes. The issue provides a project overview, a prioritized list of tasks, and specific PR submission rules.

This issue aims to enhance the RFC scanner by announcing significant lifecycle changes (decisions, target, status, needs-decision) within the RFC's thread when in rich mode. It also includes functionality to edit the card and thread title upon retitling an RFC and to suppress duplicate RFCs opened by the same author.

This issue proposes implementing a system to carry bounded activity events (stage hops, opens, merges) from spokes to the hub. The hub will maintain a fleet-wide in-memory ring of these events, keyed by hive, to enable animations and merge toasts. This is a continuation of a larger RFC and builds upon previous implementation steps.

Animated images on the Kanvas Collaboration page are horizontally clipped on mobile viewports with a width of 360px. This issue prevents users from seeing the full content of the animations, impacting the visual presentation of collaboration features.

This issue proposes enhancing a GitHub scanner to post one Discord thread per RFC, ensuring idempotency and reconciliation through durable mapping of message and thread IDs. It also includes an opt-in mechanism for posting a GitHub backlink only after the Discord thread is successfully created, respecting rate limits and avoiding duplicate announcements.

A bug exists where the 'Copy link' functionality in the activity monitor incorrectly removes 'density' and 'shift' parameters from the generated URL. The documentation also fails to mention this limitation, leading to confusion for users. The fix involves either updating the link generation logic to preserve these parameters or clarifying their omission in the documentation.

This issue is a beginner-friendly task for Hacktoberfest, asking contributors to add a new Japanese example sentence to a JSON file. No coding knowledge is required, and the contribution can be completed directly in the browser within a minute.

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 involves correcting a docstring in the `setup.py` file. The docstring currently references an outdated internal library name, `py_scripting`, which needs to be updated to reflect the current naming convention.

This feature request aims to extend the `jtd` (JSON Type Definition) to support non-string integral keys in protobuf map fields. Currently, `jtd` only supports string keys for maps due to JSON's limitations, but protobuf allows integral types. The proposed solution involves adding an optional 'key' argument to the `jtd` schema to specify the key type for protobuf map generation.

This issue describes a bug where list-type configurations in Oper8 cannot be overridden by environment variables. This is due to the `aconfig` library ignoring list types, preventing users from customizing important settings like `supported_versions`. The desired behavior is for list configurations to be fully configurable, either through environment variables or an alternative config file.

The user is encountering a `RuntimeError: dictionary changed size during iteration` when attempting to use the `import_tracker` tool to analyze the dependencies of the `torch` library. This error occurs within the `import_tracker`'s internal logic for setting ending modules, suggesting an issue with how it iterates over module attributes while potentially modifying them.

This issue involves implementing the spoke-side logic for publishing bounded activity digests as defined by a previous RFC and contract. It requires building the activity block from existing data, adhering to specific contracts regarding item limits, ordering, and privacy, and implementing coalesced updates with backpressure to avoid redundant data transmission.

This issue proposes adding a read-only "Fleet activity" page to the hub, accessible at `/activity`. It will display merged board data from an API endpoint, reusing existing UI components for row presentation and incorporating a "Hive" column with color chips and status indicators. The page aims to provide visibility into spoke activity without offering any action menus.

This issue requests the addition of a remap option for the NumPad decimal point key in the Keyboard Manager. Currently, this key functions as 'Delete' when NumLock is off, but it's not available for remapping, hindering users with keyboards that lack a NumLock toggle or those who rely on this functionality for directional input.

The `replay_execution`, `restart_execution`, and `resume_execution` functions in Kestra are incorrectly picking an old execution instead of the latest one when no specific execution ID is provided. This is because the `/executions/search` endpoint returns executions oldest first by default, and the `get_latest_execution` function is not sorting the results, leading it to select the newest of the oldest 25 executions.

This issue proposes adding a new WordPress data-source connector to the cognee project. The connector should support authentication via application passwords, ingest posts, pages, and comments, and implement incremental synchronization and deletion handling. The goal is to expand cognee's data source capabilities, with a focus on making custom post types configurable.