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 aims to improve the frontend's ability to recover pending or refundable swap orders after a page reload. It proposes fetching this order state from the coordinator API, ensuring users can always see and act on their transactions, rather than relying solely on local browser storage.

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 namespace picker in Radar currently provides misleading information to users who cannot list namespaces due to RBAC restrictions. This issue proposes updating the picker's UI to accurately explain the situation and guide users towards the correct workaround: explicitly providing namespaces via command-line arguments or configuration files.

The user is requesting that the 'file' field be excluded from consistency checks in JabRef. They argue that while 'url' and 'eprint' are desirable for consistency, the 'file' field is not realistically present in all entries and therefore shouldn't be flagged as an inconsistency. This change aims to reduce false positives in the consistency checker.

The user's profile page incorrectly displays the hardcoded text 'Email' in the contact section instead of the signed-in user's actual email address. The expected behavior is to show the current user's email when it is available.

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.

Seven platform builds are currently unassigned, meaning no single person is responsible for testing and maintaining them. This has led to bugs that go unnoticed until users discover them, as the automated CI checks only verify compilation and basic structure, not actual platform behavior. The issue seeks owners for each platform to ensure their proper functioning.

This feature request aims to expand the authentication system to support multiple users beyond the current limit of one admin and one user. This is necessary for teams larger than two, as it will eliminate the need for shared passwords, improve audit logging by identifying individual actions, and potentially enable future features like Row-Level Security (RLS). The proposed solution involves creating only an admin account on initialization and allowing user accounts to be created within the application subsequently.

This issue is a follow-up to a previous API rework, focusing on completing unfinished tasks. It involves verifying a bug fix, integrating changes from a specific pull request, discussing specific API endpoints (TX.START/END, STATION.DESELECT/CLEAR_TEXT), and potentially adding new scheduling endpoints.

This issue is a meta-issue tracking the enhancement of documentation for various probability distributions. The goal is to include detailed mathematical explanations and implementation specifics for each listed distribution. Several distributions have already been addressed, as indicated by the checked items and associated pull request numbers.

This issue seeks to improve the readability and visual consistency of text and icons on background images. The current design has inconsistent styling, with text having an outline while icons do not. The user requests options for customizable borders and shadows for both text and icons to enhance the aesthetic.

This issue proposes adding a new 'difference mode' to an image viewer (iv). This mode would visually highlight the absolute difference between the currently displayed image and the previously viewed image. The goal is to provide a clear visual representation of changes between images.

Users are reporting that when using Alt+Tab to switch between windows, the Windows Terminal application is behaving unexpectedly. Instead of cycling through windows normally, a second instance of the terminal window appears to be appended to the Alt+Tab stack, requiring additional key presses to access the correct terminal window.

The user is reporting an issue with the walking animation of a "Giant/Titan" character, specifically pointing out that the legs in frame 008 appear to be drawn incorrectly. They believe the left leg is too far back and both legs should be closer together, with one leg also appearing too large and outside the expected viewing perspective.

The `ListCampaignArchives` endpoint in the v6 branch incorrectly and destructively deletes older campaign archive revision directories and their wiki snapshots on every GET request. This is likely a bug from a one-time migration intended for engine initialization, not a read path, and lacks any backup or confirmation.

This issue seeks community assistance in completing the reverse engineering and matching of original x86 code for the game Crimsonland. Contributors are needed to refine C/C++ reconstructions of specific functions to achieve an exact match with the original compiled code, following a provided workflow and documentation.

This issue proposes replacing manual C/C++ standard settings in CMakeLists.txt with the `ament_cmake_ros_core::ament_ros_defaults` target. This change aims to ensure consistent and ROS distribution-appropriate C/C++ standard versions across packages. The process involves updating package.xml, removing manual standard settings, finding the new target, and linking against it for all library, executable, and test targets.