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.

This issue requires refactoring tests within `test_pydantic_ai` to eliminate the use of internal functions, specifically `_set_input_messages`. The goal is to ensure all tests exclusively utilize public APIs and functions, aligning with best practices for test maintenance and stability.

This issue serves as a central tracking point for the results of the nightly test suite. It outlines how to interpret the provided data, including trend tables, regressions, and improvements, and specifies the locations of raw results and comparison scripts within the repository.

This issue proposes to prevent CI tests from running when only documentation files are modified. The goal is to reduce flakiness and save CI resources by skipping unnecessary test executions for documentation-only changes.

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.

A test for doctor slash commands is failing because it passes a bare `SimpleNamespace` object to `main_callback`, which expects a `typer.Context` object with a `meta` attribute. The fix involves switching the test to use `typer.testing.CliRunner` to ensure a proper `Context` object is used, preventing future synchronization issues.

This issue addresses a bug where the DeepSpeed + LoRA combination fails with most trainer wrappers, except for sft.py, due to an empty no-decay optimizer group. The fix involves applying a shared guard function to all trainer wrappers to prevent this failure, ensuring consistent behavior across different training configurations.

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.

The default sort order for expenses in the "Spend" section of the Expensify app is currently descending by date, which is incorrect. The expected behavior is to have the default sort be ascending by date, with no pre-sort from previous actions.

This issue requires updating specific scene files within the 'song_sanctuary_3' lore quest. The update involves replacing an old tile resource (`tiles/elevation.tres`) with a new one (`tiles/elevation_2.tres`) as per a previous issue's description. This is a straightforward asset replacement task.

This issue requests that proposal filtering options (specifically 'Origins') should be hidden if there are no proposals associated with that origin within a given process. The goal is to improve the user experience by decluttering the filter sidebar when certain filtering criteria are irrelevant.

This issue reports a Denial of Service vulnerability in the Multer package, affecting multiple Backstage backend packages. An attacker can exploit this by repeatedly aborting file uploads, leading to orphaned files accumulating and exhausting disk space. The vulnerability stems from incomplete cleanup of uploaded files when a request is aborted before a file path is assigned.

This issue reports incorrect fade directions in the 'Dev Archipelago' section of the game, specifically affecting teleporter transitions. The fades are not aligning with player movement, leading to a disorienting experience. The reporter provides examples and a list of scenes to check for similar issues.

The terminal composer currently provides no visual distinction between slash commands and regular messages, making it difficult for users to differentiate them before pressing Enter. This feature proposes to visually highlight the command token in the terminal composer, similar to the web composer, to improve clarity and prevent confusion, especially with skill commands.

This issue proposes centralizing the SECURITY.md file for the organization by leveraging GitHub's community health file feature. Instead of having individual SECURITY.md files in most repositories, a single SECURITY.md file will be placed in the organization's `.github` repository, which will then be inherited by all other repositories. This aims to streamline security policy documentation and reduce duplication.

The prefetch scripts for Hermeto are failing silently when attempting to change ownership of root-owned output files. This leads to subsequent permission errors when trying to clean up or merge these files, breaking GitHub Actions prefetch steps and local hermetic reuse.

This issue proposes integrating the `turbojpeg` library to accelerate CPU image decoding within the PyTorch DataLoader. The goal is to overcome a bottleneck caused by standard decoding methods, which leads to GPU underutilization. The implementation should decode JPEGs directly to NumPy arrays, integrate with the existing Albumentations pipeline, and gracefully fall back to other decoders if `turbojpeg` is unavailable or the image is not a JPEG.

The project currently pins the `pytest` version for its Redis tests, as unpinning it leads to test failures. These failures appear to be caused by data leaking between tests, a behavior that might have changed in `pytest` version 8.0.0. The goal is to investigate this change and determine if the `pytest` version pin can be safely removed.

This issue proposes adding a user-configurable toggle to disable alarm chimes for critical tasks within the dashboard. The toggle's state should be saved in localStorage, and the sound engine must respect this setting before playing any chimes.

This issue describes a discrepancy where an integration test asserts a model-level `defaultReasoningEffort` that is not currently implemented in the `get_generator_model` function. The task is to modify the code to honor this model-level default when no specific per-request or agent effort is provided, ensuring the existing integration test passes.

This issue proposes adding an integration for Elasticsearch to Sentry, as it's a popular database currently lacking out-of-the-box support. The request is seeking community interest via 👍 votes and is labeled as 'Help Wanted' and 'New Integration'.

This issue identifies a flaw in a test case within the `spec-kitty` project. The test `test_non_volatile_lifecycle_types_broadcast_nothing` does not accurately verify the specific early return condition it's intended to check. Instead, it asserts observable states that can be reached through multiple different code paths, making the test insensitive to the intended behavior. The proposed solution is to modify the test to explicitly check for a log message indicating the early return, ensuring it specifically validates the intended logic.

This feature request asks for the addition of a filter to the HTML output of container scanning results. The filter should allow users to display only vulnerabilities that have a "fix available" or "partial fixes available", eliminating the need for manual visual scanning.

The user is encountering a "MySQL server has gone away (2006)" error during a fresh installation of GLPI version 12RC, both via CLI and web. This occurs after the database structure is created and default data is imported, specifically when attempting to update the `glpi_forms_destinations_formdestinations` table. The user notes that an older GLPI 11 instance on the same server is functioning correctly.

This issue proposes adding a new data-source connector for Postman to the cognee-community project. The connector should handle API key authentication, ingest collections, request descriptions, and documentation, and support incremental syncing and deletion.