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 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 concerns the limitations of the local operation's reach certification in a geometric modeling system. Currently, it's only certified for simple surface pairs (plane-plane, plane-quadric) and uses a sampling method that can result in inaccurate bounds for curved surfaces. The goal is to develop a more robust certification method that provides an upper bound for all surface pairs, enabling operations on more complex geometries like tori, B-splines, and blends.

The user is reporting that the Telescope application is utilizing the dedicated GPU (DGPU) for rendering, even though they have explicitly configured it to use the integrated GPU (iGPU) in the system settings. This is leading to increased heat, power consumption, and fan noise.

This issue is a beginner-friendly task to add a new color theme called "Hanami Pink" to the KanaDojo project. It requires no coding and can be completed directly in the browser by editing a JSON file, making it ideal for Hacktoberfest contributions.

The Mobile Task Composer's Codex model discovery mechanism incorrectly ignores user-defined `CODEX_HOME` and custom executable paths. This leads to the composer using default paths instead of the user's configured setup, potentially causing it to fail, use the wrong model catalog, or miss the intended default model. The fix should align Codex discovery with the cmux session's configuration for a consistent user experience.

A common End-to-End (E2E) test suite for GNOME is failing across multiple pull requests in the `projectbluefin/common` repository. This widespread failure suggests a shared root cause, such as an issue with the base branch, workflow, pinned action, or runner image, rather than individual code changes. The issue is being tracked centrally to address the underlying problem efficiently.

This issue requests the addition of focused PHP unit tests for the `CustomFieldDefinitionService` in ChurchCRM. The tests should cover the `find`, `move`, and `delete` operations for person and family custom fields, ensuring proper handling of edge cases like unknown fields, invalid directions, and deletion scenarios. The goal is to improve test coverage for this recently introduced service.

This issue addresses a potential race condition in custom field reordering when multiple requests happen concurrently. The current implementation might use stale position data due to a lack of locking, leading to inconsistent field order. The task involves adding a regression test and ensuring the reordering logic is robust against concurrent operations.

This umbrella issue consolidates several technical debt tickets related to modernizing the persistence layer, including migrating from legacy JDBC to JPA and addressing fragmented DAO classes. The goal is to declutter the open issue list and prepare for future focused migration efforts.

This issue consolidates multiple maintenance tickets related to migrating legacy `*2Action` classes in Struts. The goal is to replace field-level initialization using `SpringUtils.getBean(...)` with constructor injection, improving code maintainability and reducing technical debt. The migration will be done module by module, preserving existing functionality.

This issue serves as a meta-issue to track various frontend modernization efforts that are not immediate bugs. It consolidates existing issues related to typography normalization, resizable UI panels, print/fax layout improvements, and attachment management modal investigations, aiming to improve the overall user experience and maintainability of the frontend.

This issue consolidates several low-urgency technical debt tickets related to SonarQube findings and maintainability cleanup across different modules. The goal is to address code smells and improve readability without altering existing functionality, with the intention of splitting these tasks by module later for focused development.

This is an umbrella issue to consolidate smaller, granular tasks related to dependency, documentation, and tooling maintenance. It aims to improve hygiene and address follow-ups for Docusaurus and npm tooling, batching these efforts into regular maintenance windows.

The developers need owners of PRIME 4 G2 or SYSTEM ONE devices running EngineX OS to provide specific partition size information from their devices. This data is crucial for fixing an issue where the `/data` partition might not be correctly sized, potentially causing on-screen updates to fail due to insufficient space.

Seven files in the repository contain incorrectly encoded UTF-8 characters, appearing as mojibake (e.g., '—' instead of '—'). This issue affects two strings displayed on the repository's Overview page and stems from a process that decoded UTF-8 as cp1252 and then re-encoded it. The problem is not currently caught by existing tests.

This issue addresses a bug where effect-based buttons (`Neo.button.Effect`) do not properly communicate their pressed state to assistive technologies. The fix involves updating the `Neo.button.Effect` component to default its `pressed_` property to `null` and correctly render the `aria-pressed` attribute based on the button's state, ensuring accessibility for toggled buttons.

This issue requests native speaker reviews for the Spanish, French, Italian, and Russian interfaces. The current translations were machine-generated and lack human linguistic validation, despite checks against style guides and glossaries. Native speakers are needed to ensure accuracy, appropriate tone, and correct handling of language-specific nuances like plurals and address forms.

This issue proposes adding support for AMD AMF, Intel Quick Sync, and NVENC AV1 hardware encoders to the ff4d tool. This would allow users with AMD or Intel GPUs, and NVIDIA RTX 40-series owners wanting AV1, to utilize faster hardware encoding instead of relying on CPU-based methods.

This issue proposes adding functionality to the Power BI operator in Airflow to wait for an ongoing manual refresh to complete before starting a new API refresh. The suggested implementation involves checking the refresh history and using a deferrable operator to wait for the current refresh to finish, preventing potential conflicts.

This issue requests adding automated Cypress tests for the password strength meter specifically when it appears during a forced password change. The goal is to ensure the meter's behavior (hidden initially, showing weak/strong feedback, and hiding when cleared) is covered, without altering the password policy or other related features.

This issue describes a bug where the text size and padding of a "Card Analysis" widget remain small even after the widget is resized to a larger dimension. The provided patch includes a test case to verify this behavior, and the issue notes that it existed before the current pull request and might need to be split off.

This issue requests community testing of a game build on various GPU architectures (AMD, Intel, and different NVIDIA cards) to identify driver-specific issues versus core game problems. Testers are asked to build the game, run it to a certain point, and report their GPU, driver version, OS, progress, and logs.

This issue proposes updating the contributor guide (`CONTRIBUTING.md`) to explain the concept of contributor "standing" (rungs and badges) and the purpose of claiming tasks. It also aims to improve the pull request template to include information about the AI model used for AI-authored pull requests, which is currently missing and hinders effective review. The fix involves adding a new section to the contributing guide and potentially modifying the pull request template.

This issue describes a bug in the Databank mod where its `PostShaderInstance` incorrectly assumes the depth buffer format of the main render target. When other mods alter this format, Databank's `glBlitFramebuffer` operation fails with a `GL_INVALID_OPERATION` error, leading to log flooding and potential game freezes. The root cause is the lack of depth format checking before copying the depth buffer.

This issue proposes optimizing combat scenarios for five specific encounters (Tunneler, Waterfall Giant, Entomancer, Ink Blob, Knight Gang) in version 0.47.x. It prioritizes fixing existing bugs before proceeding with these optimizations, providing detailed reports and static evidence for each encounter to guide the implementation.

The user requests that the "What's New" feed in NewPipe should not display a blocking loading screen when refreshing. Instead, they suggest relying on existing notifications to indicate the progress of fetching new videos, allowing users to continue browsing or watching content.

The user is reporting that the "report an issue" flow on GitHub, specifically for feature requests, incorrectly links to the SS14 (Space Station 14) project instead of the intended destination. This suggests a configuration or routing issue within the GitHub repository's issue reporting setup.

This issue requests the addition of a Graphical User Interface (GUI) to the project. It is labeled as an enhancement and is seeking community contributions, indicating it's a feature request rather than a bug fix.