Find meaningful ways to contribute

The user is inquiring about plans to expand the protocol support in matterircd, noting that Matterbridge supports many more protocols. They are asking what would be required to add these protocols and express dissatisfaction with existing solutions for certain platforms.

This issue addresses race conditions in how GitHub status comments are updated and created by multiple writers. It proposes a single, authoritative writer function that serializes writes per repository, uses a compare-and-retry mechanism to handle concurrent edits, and includes reconciliation for duplicate comment creations. This is crucial to prevent lost updates and duplicate status comments, especially before implementing issue-side consolidation.

This issue proposes enabling offline verification of signed bundles by leveraging the inclusion proof already present within the bundle. The goal is to allow a verifier to confirm a signature's existence in the transparency log without needing to connect to the public Rekor log, thus improving verification speed and reliability.

This issue proposes updating the Astro build tool from version 5 to version 7. The reporter has confirmed they've taken standard troubleshooting steps and searched for existing issues. This is a straightforward dependency update task.

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 proposes adding support for custom Rekor URLs in the Anchor tool. Currently, the tool only supports the public Rekor instance, preventing teams with private Sigstore deployments from using it. The proposed solution involves adding a `--rekor-url` flag and a corresponding environment variable to allow users to specify their own Rekor instance.

The local `log-index.json` file grows indefinitely, impacting performance as it's read on every lookup. This issue proposes implementing a strategy to bound the size of this file, such as retaining recent revisions and identity rotations, or compacting older data, without compromising the integrity of historical chain verification.

This issue requests updating the "Getting Started" documentation with consistent and platform-agnostic Console screenshots. The goal is to replace installation-specific images with generic ones, ensuring clarity across different deployment environments like k3d, Kubernetes, and Amazon EKS. The update involves auditing all Console sections, capturing specific workflow steps, and reusing shared screenshot snippets.

This issue requests a review of the README's quick start guide on a clean environment to identify any unclear steps, missing prerequisites, or incorrect command usage. The goal is to ensure a smooth onboarding experience for new users by fixing any issues found before the signing steps.

This issue requests an audit and testing of the opentelemetry-instrumentation-kafka-python library. The goal is to ensure its correctness and reliability, likely involving reviewing the code for potential issues and writing or improving test coverage.

This issue announces a significant codebase migration for the niri project, merging a large refactoring effort. While aiming for parity, users are encouraged to report any breaking changes encountered in their configurations, with specific examples provided for hot corners and color/gradient styling.

This issue proposes adding essential development infrastructure to the Anchor repository. It requires implementing a GitHub Actions CI workflow for Go code, creating a CONTRIBUTING.md file to guide developers, and a SECURITY.md file for vulnerability reporting. The goal is to improve code quality, developer onboarding, and security practices.

This issue reports a false positive in Psalm's type reconciliation. Psalm incorrectly assumes that the output of a `__toString` method will always be lower-cased, leading to an unnecessary `strtolower` call being flagged as redundant. The fix involves correcting Psalm's understanding of `__toString` return types.

This issue requests the addition of comprehensive unit tests for the `internal/diff` and `internal/predicate` Go packages. The tests should cover various scenarios for schema comparison and in-toto predicate generation, ensuring the packages function correctly and handle edge cases.

This issue proposes adding a new `Bool` parser function to handle YAML 1.1 boolean values like 'yes', 'no', 'on', and 'off' (case-insensitive) which are not correctly interpreted by the current YAML parser. This fix is needed to accurately detect findings in GitLab CI configurations for `interruptible` and `allow_failure` keywords.

This issue proposes adding comprehensive tests for the `internal/canon` package, which is responsible for schema canonicalization and hashing according to RFC 8785. The goal is to ensure that equivalent schemas produce the same hash and different schemas produce different hashes, which is critical for the integrity of the Anchor system. The tests should cover RFC 8785 examples and specific cases relevant to tool schemas.

This issue proposes integrating Steinberg's command-line `validator` tool into the Continuous Integration (CI) pipeline. The goal is to automate the process of running VST3 unit tests, replacing the current manual build and execution steps.

This issue identifies a correctness problem where a mutex (Store.mu) is held across paginated GitHub API calls, potentially blocking all producers in the process. The fix is dependent on another pull request (#16291) which introduces the relevant code.

This issue aims to improve the `withoutSudo` function by enabling it to correctly parse various `sudo` and `doas` command-line arguments. The current implementation incorrectly identifies the command to be executed when combined flags, long options, or specific `doas` arguments are used, leading to potential security rule misinterpretations. The goal is to extend the parsing logic to handle these cases accurately.

The `isProdEnv` function incorrectly identifies environments as production-like if their names contain substrings like 'prod' or 'live'. This leads to false positives for environments like 'non-prod' or 'products-review'. The proposed fix involves implementing word-based matching and excluding 'non-' prefixes for 'prod' and 'production' to accurately classify production environments.

This issue requests that all in-game icons be updated to match the style of the base game. It provides examples of existing icons for worldwide rooms, personal rooms, time trials, and race courses, along with screenshots of where these icons are used. The goal is to ensure visual consistency across the game's interface.

This issue highlights a change in the `Journal.Get` function where it no longer blocks to refresh data when a peer process holds a flock. Instead, it now falls back to the last committed snapshot, potentially leading to stale data for callers relying on immediate cross-process freshness. The change is documented as intended, but the issue asks to confirm if any callers require the old blocking behavior.

This feature request proposes adding an option to assign hardware buttons (like those on headphones) to skip forward or backward through podcast chapters. This would provide a more convenient way to bypass unwanted sections like ads, without needing to manually interact with the app. The suggestion includes a fallback mechanism to fast forward/rewind if a podcast doesn't have chapter markers.

This issue proposes adding concrete implementations for various node types in the visual builder. Currently, these nodes are primarily visual/metadata and need to be backed by functional code to generate usable Burr actions, covering LLM calls, API calls, inline code execution, streaming, and control flow logic.

This issue aims to significantly automate and mature the project's release process. It identifies several manual steps and gaps in current tooling, proposing solutions for RC promotion, release branches, backports, reproducible builds, and release notes generation to make the process more reliable and less error-prone.

This issue is a beginner-friendly task to add a new Japanese proverb to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute. It's marked as a 'good first issue' and eligible for Hacktoberfest.

The current implementation of simple span and log processors in OpenTelemetry does not properly handle in-flight exports during shutdown or force flush operations. This can lead to data loss as exports might be sent to an already shut-down exporter. The proposed fix involves tracking active export jobs, ensuring they complete before shutdown, and adding timeouts to prevent indefinite blocking.

The current implementation of the TraceParent header decoder rejects entire headers if they contain any uppercase characters, even in future, unknown fields. This behavior contradicts the W3C Trace Context specification, which states that unknown fields should not be parsed or assumed. The proposed fix is to remove the blanket uppercase rejection and ensure only known fields are validated for lowercase hex.

This issue proposes adding a new API endpoint, GET /v1/vehicle-anomaly-episodes/{episode_id}, to retrieve detailed information about a specific vehicle anomaly episode. The endpoint will provide data such as the anomaly type, vehicle ID, timestamps for opening and closing, duration, and the reason for closure, supporting use cases for investigating vehicle issues.

This issue proposes adding a new API endpoint, GET /v1/vehicle-anomaly-episodes, to retrieve detailed information about vehicle anomalies. This will allow operators to investigate specific issues like stale timestamps or implausible positions, which are not visible in aggregate metrics. The endpoint will support various filtering parameters to narrow down the search.