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.

An agent deletion fails with a 404 error when the SkillCore is disabled because the deletion process incorrectly interprets the absence of the Skill module as an error, rather than an empty skill set. The expected behavior is for the deletion to proceed if no skills are attached, treating the SkillCore absence as a valid state for agents without skills.

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 adding Homebrew distribution for the project's binaries. This would involve configuring GoReleaser and GitHub Actions, and could help circumvent macOS's security warnings for unsigned binaries downloaded from the releases page.

This issue proposes adding adapters for Microsoft's AutoGen and Semantic Kernel frameworks to gitagent. The goal is to enable gitagent to export code compatible with these enterprise-grade agent frameworks and execute agents within them, bridging the gap for teams using Microsoft's AI ecosystem. The scope includes potentially supporting one or both frameworks, with acceptance criteria focusing on code generation, agent execution, and documentation.

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 `assertObjectPathShape` helper function is duplicated across nine different provider files. This issue proposes to consolidate these definitions into a single file and import it where needed. A minor challenge is that one file uses a different parameter order, which will need to be standardized.

This issue proposes to automatically generate Git commit messages in JabRef based on the actual changes made to the library. Instead of a static message, the system should analyze added, modified, and deleted entries, providing a summary like 'Add 3 entries, modify 2 entries'. A bonus feature suggests more specific messages for single-field changes within an entry.

This issue outlines a "Project Joy" initiative for the next six months focused on addressing all minor annoyances within the 'kew' project. Developers are encouraged to create individual issues for small bugs, glitches, or UI problems, or to discuss them directly in this thread.

This issue requests the addition of a Brazilian Portuguese README file (`README_pt.md`) to the repository. The new file should be a concise translation, mirroring the structure and length of existing localized READMEs, and should include the main pitch, engine list, install table, and quick start sections. Additionally, the language switcher in the main README and other localized READMEs needs to be updated to include a link to the new Portuguese version, and the `readme-check.mjs` script must be updated to include the new file in its drift guard.

The 'Change version state' dialog incorrectly displays the 'SUNSET' version state as 'Unknown'. This is because the `stateToLabel` function in the UI code does not have a specific case for handling the 'SUNSET' state, causing it to fall through to the default 'Unknown' label. The issue is limited to the dialog's label, as the 'SUNSET' state is not intended to be a selectable target state.

This issue requests support for the Sagemcom FAST3896-15 WLAN cable modem used by PYUR. The user has provided detailed modem information, including firmware, DOCSIS version, and a HAR file for network capture. They are willing to assist with testing and debugging to get this modem working with the docsight project.

This issue proposes to update the `platformio.ini` file for the ESP32-S3-N16R8 board to specify a 16MB partition table. This change will allow for better utilization of the available flash memory, enabling features like proper OTA updates and a larger SPIFFS partition for web interfaces and data.

This issue aims to enable adaptive thinking for Bedrock applications using specific ARN formats that currently do not support it. The problem arises because the model name is not directly present in these ARNs, preventing a regex check from matching. The fix involves registering these ARNs with LiteLLM to correctly identify them as supporting adaptive thinking.

This issue is a follow-up to a previous code cleanup effort that enabled Ruff's G004 linting rule. The task involves converting f-string formatted log messages within a specific Python file (`benchmarks/storage_backend_io/storage_backend_io_benchmark.py`) to the older, but preferred for logging, %-style formatting. After the conversion, the corresponding ignore entry in `pyproject.toml` should be removed.

When a team member or user is removed, their associated Agents become orphaned because the `owner_user_id` becomes invalid. This prevents any role, including administrators, from deleting these orphaned Agents. This leads to orphaned Agents appearing in the UI, their associated skills becoming unusable, and a UI/backend authorization mismatch, ultimately requiring manual intervention to clean up.

This GitHub issue announces a challenge to rigorously test the mathematical reasoning capabilities of the Spark-X2.5 language models. Participants are required to download the models, conduct evaluations on math benchmarks or specific problem types, and publish their reproducible results on Hugging Face Discussions. Submissions are open from September 7th to September 13th, 2026, with judging and awards following.

The API's Cross-Origin Resource Sharing (CORS) is configured to allow requests from any origin, posing a security risk. This issue requires updating the `app.js` file to implement an explicit origin allowlist, likely using environment variables, to restrict access in production environments.

This RFC proposes adding continuous quantization support for various models and methods, aiming to improve efficiency. It outlines a "Quantization Matrix" to track supported models and components, and specifies hardware requirements for contributors to validate their work. The issue also includes a table detailing specific model/method combinations and their quantization status.

The Admin Audit tab is silently omitting security-critical denial events recorded by the proxy. These denials, such as unauthenticated requests or non-admin access to admin routes, are correctly logged to stdout but are not visible in the UI, misleading operators about the system's security posture.

The `CutoffFhSplitter` is failing contract tests, likely due to a pandas 3 incompatibility. The issue requires investigating the failure, potentially fixing the splitter or adjusting the test API contract if it's too restrictive. Once resolved, test skips related to the splitter should be removed.

The `SameLocSplitter` is failing contract tests, indicating a potential bug in its implementation or an overly restrictive API contract. The issue requires investigation to fix the splitter or adjust the tests, and then remove any associated test skips.

The Simplified Chinese README file has never been reviewed by a native Chinese speaker since its creation. This issue requests a proofreading pass to correct unnatural phrasing, incorrect register, and mistranslated terms, ensuring the content is accurate and natural for a Chinese developer. Contributions can be made via a pull request with fixes or by listing suggested changes in the issue comments.

This issue aims to standardize the "Back" caret header behavior within the onboarding flow. Currently, the header's animation and position are inconsistent across different onboarding steps. The proposed solution is to create a reusable, sticky header component, similar to `InteractiveStepWrapper`, to ensure a consistent user experience.

This issue requests the addition of edge-case tests for a document reader that supports various file formats (TXT, Markdown, JSON, CSV, PDF, DOCX). The goal is to enhance reliability and test coverage by including tests for scenarios like empty or missing files, unsupported extensions, invalid JSON, and files with Unicode characters. The tests should be added to `tests/test_document_reader.py` without altering the existing architecture.

This issue reports intermittent, unreliable failures occurring on NetBSD systems running on ARM architecture. The provided code snippet suggests a mechanism to filter for these specific environments, indicating a need to consolidate and investigate these flaky tests in a central location.

NetBSD runtime tests are experiencing intermittent failures following a recent code change (CL 526118). The failures appear to be concentrated in OS thread-specific tests, suggesting a potential connection to the recent CL.

This bug report identifies a discrepancy between the Matrix v1.19 specification and the Ruma implementation for the `m.room_key` event. The specification defines the property as `shared_history`, but Ruma currently uses `m.shared_history`, which needs to be corrected.