Find meaningful ways to contribute

This issue proposes adding support for Artemis Queue Pipe bindings, building upon previous work. The goal is to integrate with the ArkMQ operator to enable communication with Artemis-based queues, similar to the existing Strimzi/Kafka integration. This involves setting up ArkMQ, defining a queue custom resource, developing Camel route logic, and implementing comprehensive unit and end-to-end tests.

This issue proposes adding a check to the `soup bench train` command to ensure that a model is actually training (i.e., has non-zero gradient norms) when performance metrics are measured. This is crucial for the meaningfulness of reported training throughput and addresses inconsistencies in how memory and step counts are recorded, as well as the inability of the current monitoring to distinguish between zero gradients and no gradient data.

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 addresses a bug where the `training.moe_lora` configuration is loaded but ignored by several training tasks (ipo, bco, reward_model, ppo, embedding). The goal is to either properly integrate MoE LoRA support for these tasks or explicitly refuse the `moe_lora: true` setting with a clear error message. This is a follow-up to a previous issue that fixed similar behavior for other training tasks.

The `deploy-test` suite failed during a nightly run, specifically on the 'workload listing shows correct data' test within the Deploy Dashboard. The failure includes a screenshot and trace, indicating a potential issue with how data is displayed in the dashboard's workload listing.

The patient profile's "Notes" tab is always visible and always displays read/write UI, regardless of user permissions. This is because the frontend code fails to implement role-based access control (RBAC) for the tab's visibility and the ability to write notes. While the backend correctly enforces permissions, the frontend does not.

Users are reporting that uv is exceeding the operating system's open file handle limit (ulimit) during package synchronization, building, and Python version uninstallation. This issue is particularly problematic on Linux and macOS where default limits can be low. The goal is to investigate why uv is consuming so many file handles compared to similar Rust tools like Cargo, which appears to manage file descriptors much more efficiently.

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.

The user reports that packages previously published to Opam are now missing. They have linked to a previous issue where the publication was discussed, indicating a potential issue with the Opam repository or the publishing process.

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.

Agentic sessions are storing full base64 image data within `function_call_output` (tool_result) items, leading to significant database bloat and making conversations unopenable in managed stores. While previous issues addressed similar problems for message and snapshot items, the source `tool_result` items are still retaining large amounts of raw image data.

This issue addresses broken multi-line installation commands in the "Introduction to Observability" learning path's first exercise. The Prometheus download and Grafana setup commands are incorrectly split, leading to terminal errors and 404s. The issue also notes maintenance debt due to brittle OS-specific scripts and outdated version pinning.

This issue proposes automating the retrieval of supported version information for `eslint-markdown` within the project's documentation. Currently, this information is updated manually, leading to potential errors and increased maintenance effort. The proposed solution involves modifying a VitePress theme file to dynamically fetch these versions and updating the installation documentation to utilize this new automated retrieval.

This issue proposes replacing the embedded etcd in K8E with a new backend: rqlite for consensus and persistence, combined with a Zig implementation of the etcd v3 compatibility layer. This aims to maintain a self-contained deployment experience while leveraging a more mature consensus mechanism. The Zig layer will handle etcd v3 semantics like MVCC, transactions, watches, and leases, interacting with rqlite via its HTTP API.

This issue proposes to remove code that supports a deprecated feature, "synthetic Kits." The feature was previously deprecated in another issue (#5803), and this task is to clean up the remaining implementation.

This issue proposes an optimization for the pipeline log tab, aiming to improve its user interface or functionality. The accompanying image likely showcases the current state and the proposed changes for better log visualization or interaction.

The feature card animation on the Operate Your Infrastructure page does not automatically trigger on mobile devices. The animation should play when the card enters the viewport, and tapping the card should still navigate to its linked page. This issue is tagged as a bug and is open for contributions.

This issue proposes an enhancement to learned sparse retrieval models by storing the model's confidence score for each generated term alongside the term itself in the index. Currently, the system generates related terms but treats them with equal weight, losing valuable information about the model's certainty. Implementing this would allow for more accurate scoring and retrieval, leveraging the benefits of learned sparse models within an inverted index structure.

This issue proposes adding write capabilities to the Plex adapter for the `fix_metadata` feature, which currently only supports Jellyfin. The Plex adapter is read-only, and implementing this requires understanding and interacting with undocumented Plex API endpoints for matching, pinning, and refreshing metadata. The work is blocked by the need for a Plex server owner to test and verify the implementation.

This issue requests the addition of Swagger decorators to the `email-template.controller.ts` file. The goal is to group the controller's endpoints under a specific tag and provide concise summaries for each operation in the generated API documentation. This will improve the browsability and understanding of the API for developers.

When running `spec-kitty next` in query mode without `--result`, a charter preflight failure is incorrectly logged with `consumer=dashboard` instead of the expected `consumer=next`. This happens because the query mode reuses a dashboard helper function that hardcodes the consumer label, overriding the intended `consumer=next` scope.

This issue identifies a potential leftover directory `lessons/draft/` that appears to be unused, while `lessons/drafts/` is actively used as an output directory for scripts. The goal is to confirm if `lessons/draft/` is indeed a remnant, delete it, and clean up related configurations. If it's not a remnant, its purpose needs to be clarified.

This issue proposes adding a new linting rule that enforces a configurable number of blank lines above and below Markdown headings. The rule should support per-heading-level configurations and include an autofix to insert missing blank lines, mirroring the functionality of `markdownlint`'s `MD022` rule.

This issue requests an improvement to the `consistent-code-style` rule in `eslint-markdown`. Specifically, it aims to refine the reported error locations for the `blankLineAbove` and `blankLineBelow` options to be more precise and consistent with existing style guidelines.

The PR-Agent currently installs all provider SDKs regardless of which Git provider is actually used, leading to unnecessary dependencies and larger installations. The proposed solution involves making provider resolution lazy and moving SDKs into optional extras in `pyproject.toml` to allow users to install only the necessary providers.

This issue proposes integrating additional OCR engines into JabRef by leveraging OCRmyPDF's plugin system. Currently, JabRef supports Tesseract and Docling for OCR, and the goal is to expand this by incorporating other OCR engines available through OCRmyPDF plugins.

This issue is a beginner-friendly task to add a new common Japanese learner mistake to a JSON file. It requires no coding and can be completed directly in the browser by forking the repository, editing the specified JSON file, and submitting a pull request.

This issue is a beginner-friendly task to add a new Japanese "false friend" pair to a JSON file. It involves adding the terms "手紙 (tegami)" and "letter (English)" with an explanation and example to prevent common language mix-ups. No coding is required, and the contribution can be made directly from the browser.

This issue points out that the MDN documentation for `Navigator.sendBeacon` incorrectly suggests using `pagehide` as a fallback mechanism. The author states that all modern browsers now support `visibilitychange`, making the `pagehide` fallback obsolete and recommending its removal from the documentation.