Find meaningful ways to contribute

This issue proposes adding a new condition to Integration resources to indicate the presence of an associated CamelMonitor resource. This will provide a visual cue in the Kubernetes UI, managed by Kubebuilder, to inform users if an Integration is being monitored by the Camel Monitor Operator.

This issue is a beginner-friendly task for Hacktoberfest, requiring contributors to add a new Japanese grammar point to a JSON file. No coding experience is necessary, and the entire process can be completed in under a minute directly through the browser.

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 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 describes a performance problem where Gearman workers and the daemon experience high CPU usage over time, even when workers are idle. The user has provided strace logs of a worker's waiting loop, showing frequent network communication and polling, but the root cause of the increased CPU load remains unclear and difficult to reproduce.

This issue describes several problems with data dictionary functionality in the "Jimu Reports" online form filling feature. Users are unable to select existing system data dictionaries, and attempts to add new ones result in "code already exists" errors. The report also suggests improvements for static data sources, API dictionaries, and table dictionaries, including filtering and custom SQL options.

The current maintainer of the mistletoe project is looking to step down due to shifting life priorities and is seeking new maintainer(s) to take over project management tasks like code reviews and releases. They are open to new individuals or a team, ideally from the active contributor base, with the original creator ready to grant necessary permissions.

The user is reporting a failed download when attempting to update the 'openark' package from version 2.0.0 to 3.0.0. The download failed with an HTTP 404 error, indicating that the resource was not found at the specified URL. This suggests an issue with the download link in the package manifest.

The robot's state timestamps are consistently arriving approximately 4.5 milliseconds *after* the host's PTP hardware clock, despite PTP being enabled and configured for hardware timestamping. This discrepancy is observed even when the robot is stationary and the measurement directly brackets the state read with host clock readings. The issue persists across different PTP configurations and network interfaces.

The user is requesting a new feature to integrate FitBuddy with Health Connect, allowing it to read exercise and weight data from other apps like OpenVitals, Skulpt, and WeightLog. They are willing to contribute a Pull Request but lack the necessary Kotlin and Health Connect integration knowledge.

This issue proposes adding an optional feature to FitBuddy that allows users to input macronutrient values (protein, carbohydrates, fat) with one decimal place. This enhancement aims to improve tracking accuracy for users who require more precision, while keeping whole numbers as the default for simplicity. The proposed solution includes a setting to enable/disable decimal input and ensures decimal precision is maintained in daily totals.

This issue requires adding a new end-to-end test to verify the fallback mechanism for an older version of the widget (0.5.0) when interacting with a newer server. The test will involve serving the published 0.5.0 widget bundle and ensuring it functions correctly, specifically checking that it doesn't accidentally use the local development build.

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. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

This issue proposes shipping reviewed translations for the native wallet, expanding beyond the current English-only support. It outlines a phased approach for releasing translations in batches, detailing the translation workflow, required QA checks for each locale, and acceptance criteria to ensure a high-quality multilingual experience.

The `pymobiledevice3` sysmon tool encounters issues when XCUITest is active on iOS devices. For iOS 16 and below, it exits silently with code 0, making failure detection difficult. On iOS 17 and above, the fallback mechanism for sysmon fails inconsistently, leading to errors during the XPC handshake for some devices.

The `luks-e2e.sh` script's screenshot validation incorrectly accepts blank image frames. This allows for invalid screenshots to pass the gate, potentially leading to incorrect documentation. The fix involves adding a check for uniform color and a minimum size floor to reject blank captures.

This issue tracks the migration of several CRM-related modules to version 17.0 of the OCA framework. It lists modules that have been completed (marked with 'x') and those that are still pending. The issue also provides a link to the official migration guide and a FAQ for missing modules.

This issue proposes adding checksums to disk entries in a cache to detect corruption caused by disk issues or manual edits. When a corrupted entry is detected during retrieval or recovery, it should be treated as a cache miss, and the entry along with its descendants should be deleted to maintain prefix-safety. The implementation should also track corrupted entries and handle existing files without checksums.

This issue identifies a documentation error in the S2 Card component examples. Specifically, the anatomy examples for AssetCard, UserCard, and ProductCard incorrectly close the `<CardPreview>` component with `</CardView>`, leading to invalid JSX and incorrect learning for the agent skill. The expected closing tag is `</CardPreview>`.

This issue is an umbrella task to migrate existing imperative validation logic (if/throw checks) in Seatunnel's connector and transform components to a new declarative `optionRule()` system. The goal is to improve maintainability and expressiveness of validation rules using predefined conditions like numeric ranges and cross-field comparisons. This is Phase 2 of a larger effort, with the framework already in place.

This issue proposes adding a native "alert" functionality to the UIMenu system, similar to what's currently used in the BattleMenu. The goal is to display "Function not available" alerts for unimplemented features within the PauseMenu and to replace the existing alert logic in the BattleMenu with this new UIMenu system.

This issue proposes replacing C++ `#define` preprocessor directives with `constexpr` variables. This change aims to improve code quality by adhering to C++ Core Guidelines. It also notes that some Python scripts might require updates to accommodate this change.

This issue requests the addition of more comprehensive unit tests to the project. These tests should be integrated into the CI pipeline, mirroring the practices of the main Toolkit repository.

The current configuration loading mechanism incorrectly treats blank environment variables as set, bypassing default values. This leads to errors when expected values are missing, such as API URLs or fleet IDs. The proposed solution is to modify the configuration loading function to treat empty or whitespace-only values as unset, thereby enabling the fallback to default values.

A REST delete operation using MEMCLAW_TRANSPORT=rest fails on the client-side with an 'Expected JSON response' error, even though the delete succeeds on the server. This is because the Caura API returns a 204 No Content status for successful deletes, which the client's request function incorrectly expects to be JSON. The proposed solution is to modify the client to handle 204 responses gracefully by returning an empty or specific JSON object before checking the Content-Type.

The MemClaw client incorrectly treats all 4xx HTTP responses, including '429 Too Many Requests', as permanent errors, causing tool calls to fail immediately during temporary rate limiting. The proposed solution is to modify the client to retry on 429 errors with a backoff strategy, similar to how 5xx errors are handled, and optionally respect the 'Retry-After' header.

The current implementation of the MEMCLAW_API_URL check strictly enforces HTTPS, preventing self-hosted Caura instances running on localhost via HTTP from being used. The proposed solution is to allow HTTP for localhost, 127.0.0.1, and ::1 while maintaining the HTTPS requirement for other hosts.

The default MemClaw endpoint 'memclaw.net' has been retired, causing pipeline failures for users who don't reconfigure their settings. This issue requires updating the default endpoint to the new Caura endpoint across configuration files, documentation, and examples to ensure the pipeline functions correctly out of the box.

Users are reporting that color management is no longer functioning correctly in the Ente Photos Android app after upgrading to version 1.2.4. This issue affects multiple devices, including a Google Pixel and a Samsung Galaxy S21, preventing the proper display of images with non-standard color profiles.

This issue tracks the progress of getting the 'Vela' application to work with Android Auto across various Android installation methods and ROMs, including stock, GrapheneOS, and rooted devices. Different approaches like KingInstaller, AAEnabler, PlayInstaller, and Gearslip are being tested, with varying degrees of success depending on the phone's setup and the car's head unit.