Find meaningful ways to contribute

This issue proposes a phased approach to adding type hints to the `pysad.models` module. The goal is to address the 209 type hinting errors reported by mypy, prioritizing individual model detectors in separate pull requests to manage the workload. The vendored `kitnet_model` will be excluded from the checks.

This issue reports a merge conflict preventing a Pull Request (PR) from being merged. The conflict arises from changes in `src/docs/api-reference.md` clashing with a recent v6 update. The solution involves rebasing the PR and running a specific script to fix API reference citations.

The user is experiencing an issue where audio from phone calls is not being forwarded to their Amazon Fire tablet when using Wireless Helper and Android Auto. While other Android Auto features like navigation and Spotify work, call audio remains on the phone after answering on the tablet. The user is asking if this behavior is expected.

This issue highlights a critical coupling in the OTP server's self-signed certificate, where it acts as both the server certificate and the Certificate Authority (CA). This means certificate rotations break existing secrets and require careful maintenance windows. The proposed solution is to document this trust coupling in the AGENTS.md Gotchas section to provide reviewers with necessary context for future TLS-related changes.

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.

This issue tracks the migration of various Odoo modules to version 18.0. It lists the modules that need to be migrated, their current status (completed or pending), and links to related pull requests. The primary goal is to ensure these modules are compatible with the new Odoo version.

This issue aims to improve the error handling of the `olf query --file` command by adding tests for empty, unreadable, and non-existent SQL files. The goal is to ensure clear error messages and non-zero exit codes are returned before attempting to connect to a database or look up toolchains, without requiring credentials or Kubernetes.

The current maintainer of pip-review is looking for a new person to take over the project as they are no longer using it and have limited time to invest. They will continue to accept pull requests and release updates for the foreseeable future, but are actively seeking a new maintainer to ensure the project's continued development and support.

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.

The soroban-guard-cli tool incorrectly handles missing directory paths by silently exiting with success and without error. It also unnecessarily scans build and version control directories like `target/`, `.git/`, and `node_modules/`. The suggested fix involves adding path existence checks, proper error handling for directory traversal, and filtering out unwanted directories.

The PSU Control - HomeAssistant plugin for OctoPrint has been abandoned by its original maintainer. A user has forked the plugin, fixed a critical bug, added new features, and is willing to maintain it going forward.

This issue requests the addition of artwork and a gallery entry for the `catalog-designer` badge. It involves creating a new folder for badge assets, adding a PNG and SVG image, and updating a JSON file with badge information and a README entry. The goal is to recognize community members who consistently contribute verified designs to the Meshery Catalog.

A race condition in the OTLP integration test causes the collector to fail binding to a port because it's released and re-allocated before the collector can bind. The proposed solution is to bind the collector to port 0 and pass the bound listener to the server, ensuring the port remains allocated throughout the setup process.

This issue proposes a visual refresh for the home splash screen to align it with the rest of the application's modern UI. The goal is to update the corner radius and drop shadows of the splash card and suggestion buttons to match the style of the chat message bubbles. Design proposals with before/after screenshots are welcomed.

This issue describes a UI bug where the Lumen avatar is not displayed while its response is still streaming. The avatar only appears after the entire response has been received. The expected behavior is for the avatar to be visible from the start of the message rendering.

This issue addresses an inconsistency in font sizes across different UI elements in the application, specifically the chat text, SQL editor, and data tables. The goal is to implement a shared type scale to ensure a more visually cohesive and even appearance when these components are displayed together.

This issue describes a UI bug where the split collapse toggle in the output pane overlaps with chat avatars when the output pane is open. The expected behavior is for the toggle to be positioned so it never overlaps avatars, potentially by adding padding to the chat column or relocating the toggle.

This issue describes a visual bug in the Planner where the checkmark icons for completed tasks are not vertically aligned with their corresponding text labels. The goal is to adjust the styling so that the checkmarks are perfectly centered with the first line of the task description, improving the overall UI consistency.

The expand/collapse chevron icons in the planner checklist are misaligned due to varying step title lengths. The goal is to ensure all chevrons are consistently positioned on the right edge, creating a visually uniform column.

This issue proposes enabling TLS 1.3 by default on the client-side. The primary challenge is that the TLS 1.3 handshake completes on the client before the server validates the client certificate, complicating error handling and retry logic.

This issue proposes to prevent sensitive credentials from being logged by the WebhookAuditSink. Currently, the sink logs the full webhook URL, including any embedded credentials, when a POST request fails. The fix involves modifying the logging mechanism to only record the hostname and port of the webhook URL, thereby protecting sensitive information.

The nvim-dap plugin for the 'pwa-node' adapter incorrectly uses the literal string "${port}" instead of a resolved runtime port. This prevents Node.js debugging from attaching successfully as the debugger cannot connect to the expected port.

The Kepler Helm chart's NetworkPolicy template is missing common Helm labels and user-defined annotations, making it difficult to find and manage. This issue proposes adding these metadata fields to the NetworkPolicy to align with other chart resources and improve discoverability and auditability.

The user is requesting support for the `linux-musl-arm64` platform, which is currently missing. This would enable the package to be used with Alpine Linux containers on AWS ARM64 execution environments, addressing cost and performance concerns.

This issue proposes adding helper methods to modify S2000 TOU and Custom plans, building upon previous work that extracts and encodes schedule data. These helpers should allow for individual parameter updates or whole slot object modifications, while also considering device-specific limitations like maximum groups/slots and time range filling. Clarification is also needed on device local time for accurate active slot identification.

The maintainer of the proton-mail-bridge-client is seeking community testers for specific features that could not be verified with their own Proton account. They are looking for feedback on calendar invitation responses from various platforms, functionality on Windows/Linux with a real Bridge, Homebrew installation, handling of unusual mailboxes, and multi-account setups. Testers are asked to use test mail only and report their OS, Node version, Bridge version, and the command used.

This issue requests the implementation of Caller ID support in Lurker, a feature already present on networks like OFTC and Libera.Chat. This enhancement would allow Lurker to recognize and potentially display caller ID information for users.

This issue proposes adding a new 'tokenF1' metric to the @cogitator-ai/evals package. This metric will provide a more nuanced evaluation of answers by considering token overlap, similar to the F1 score used in SQuAD, addressing limitations of exact match and character-based similarity metrics. The implementation involves adding the metric to specific files, ensuring consistent normalization with an existing private implementation, exporting it, documenting it, and adding comprehensive tests.

This issue proposes moving the 'Application Pioneer' badge from the 'Achievement Badges' section to 'Archived Badges' on badges.layer5.io. This is because the badge is no longer relevant due to potential deprecation of the Applications feature and the absence of an award path in Layer5 Cloud.

This issue suggests an improvement to the rutorrent-filemanager plugin to correctly handle local executable detection when `$localHostedMode` is true. Currently, it bypasses `findEXE()` and directly uses `findRemoteEXE()`, which can lead to errors if executables are available locally but not remotely. Aligning with ruTorrent's standard behavior by checking `findEXE()` first would resolve this compatibility issue.